Problem with TelegramDesktop WebApp in i3wm #5091
Replies: 5 comments 15 replies
-
I see no reason whatsoever to assume that this has something to do with i3. Why would i3 be involved in any DBUS stuff? I'll convert this to a discussion because there's nothing to investigate on the window manager side of things. KDE isn't just a window manager. |
Beta Was this translation helpful? Give feedback.
-
Agreed, doesn't sound like this has to do with window-manager. For what it's worth, I'm using Telegram with i3 no-problemo. |
Beta Was this translation helpful? Give feedback.
-
is there any update for it? as i see on telegramdesktop/tdesktop#24953 there should be a issue. but i can't find it.
|
Beta Was this translation helpful? Give feedback.
-
I see this:
Could that have anything to do with it? |
Beta Was this translation helpful? Give feedback.
-
In case anyone needs, I finally found time to report to Qt a similar (or maybe it's actually the same) issue that manifests on mutter. It has a minimal Qt code that leads to the same observable result on mutter. Feel free to try it, if it leads to the same effect on i3, you can vote for it on Qt site, leave a comment that i3 is also affected or maybe try to debug it from i3/picom side. |
Beta Was this translation helpful? Give feedback.
-
I'm submitting a…
Current Behavior
I get this result. Just a white window and a message in the console "Could not determine the accessibility bus address" (Compton has nothing to do with)
Expected Behavior
Reproduction Instructions
Environment
Output of
i3 --moreversion 2>&-
:Config file
Logs
Telegram Logs In ~/.local/share/TelegramDesktop/DebugLog/log__.txt:
In terminal:
In journalctl:
OS and compositor
I turned to telegram desktop for help, but they sent me here
telegramdesktop/tdesktop#24953
Telegram Web Apps work great with KDE Plasma, but I don't want to switch to this one
I would like to draw your attention to the error:
It wasn't in KDE Plasma
Beta Was this translation helpful? Give feedback.
All reactions