Closed jjgalvez closed 11 months ago
As far as I understand it's either qtwayland or wayland-server trying to find first free socket ID. So it's ok.
As far as I understand it's either qtwayland or wayland-server trying to find first free socket ID. So it's ok.
How do you figure it's ok, it's still not displaying the web content, which does work on X11, and I'm still getting an error saying that another compositor may be running.
It's not a error, just a warning, if it doesn't display web content then this is unrelated. This report is closed because it's about a warning which is expected, please do a report about actual problem you have.
Steps to reproduce
start telegram-desktop under a wayland session and open a link which opens in an internal webkit view
Expected behaviour
the webcontent to be rendered within the current wayland session
Actual behaviour
Telegram-desktop seems to try to open a new wayland session and then tries to lock the existing session which it cant. The error from the terminal:
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor is running
looking in /run/user/1000 before telegram is started there is a wayland-0.lock file, opening the webview creates a second wayland (wayland-1.lock) fileOperating system
Arch, KDE Plasma 5.27.9
Version of Telegram Desktop
4.11.8
Installation source
Other (unofficial) source
Crash ID
No response
Logs