Closed fleriel closed 11 months ago
plz enable beta, restart telegram and send crash id on next start and post id here.
plz enable beta, restart telegram and send crash id on next start and post id here.
Beta was enabled, but there's no crush report for some reason
Cause it's not a crash but a Wayland protocol error which happened due to a bug in graphics drivers according to the log
Google says 0x3000 is a success code what is weird. Maybe it's related to #26366 / #26393...
Can't reproduce though. Apparently it's a bug in Intel driver but I have no Intel hardware.
Not long ago an update came out where the same error occurred when trying to open a media file, before this update everything worked fine.
That update was fixed for us wayland users, but it seems like some things went unnoticed.
does this happen with flatpak/snap build or only with static build? Both #26366 and #26393 have Intel driver instability only with static binary.
flatpak version works fine, snap version also crashes
Ok, so it's not related to those issues but a new Qt regression. Nice, no new Qt version without a regression.
I wonder what protocol error happens? Can you run with WAYLAND_DEBUG=1
?
Sure tg-out.txt
Does disabling OpenGL help? Does this happen (only) in multi-screen environment with different scale factors?
Reminding that the lack of answer will lead to issue being closed
Report from #26899 : disabling OpenGL wasn't helpful, single-screen configuration.
Looks like I reproduced with weston
Steps to reproduce
Examples
![tg_01](https://github.com/telegramdesktop/tdesktop/assets/89990325/1ae5fab4-5e86-4353-af79-4cdb923a0497) ![tg_02](https://github.com/telegramdesktop/tdesktop/assets/89990325/731b0db3-8136-4c5e-b5c0-19e05d21e998)Expected behaviour
Context menu should be closed
Actual behaviour
Telegram crashes
Operating system
Fedora Workstation 38, Gnome 44.5 (Wayland)
Version of Telegram Desktop
4.10.3
Installation source
Static binary from official website
Crash ID
No response
Logs