sublimehq
Wrong menu on initial click. KDE / Archlinux
Description of the bug
When clicking an application menu the file menu appears regardless of where you click. Correct menu doesn't appear until the mouse moves out and back into the clicked menu. And sometimes the menu doesn't appear.
Steps to reproduce
- Start ST.
- Click any menu.
Expected behavior
Clicked menu show be shown
Actual behavior
https://github.com/user-attachments/assets/961857f3-527d-4ea1-9564-b5eb2a6f0658
Sublime Text build number
4192
Operating system & version
Archlinux
(Linux) Desktop environment and/or window manager
KDE
Additional information
Seems to be related to wayland. If I force XWayland using GDK_BACKEND=x11 the issue is not present. Also while setting up and figuring steps to reproduce at one point the editor went unresponsive, couldn't type or move caret around using arrow keys or mouse. I managed to get the editor responsive again after clicking around the menus some more.
OpenGL context information
@dazoe same issue as you with ST V.4192
- others troubles like: cannot close the window the sidebare doesn't open neither shortcut nor menubare and statebar
https://github.com/user-attachments/assets/edde64fd-47ee-4e13-aa11-b8bd9a1277e0
Operating System: EndeavourOS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
The menu and window decorations are drawn by GTK and KDE respectively, so it's unlikely this is a problem with Sublime Text. Does the same thing happen for other GTK-based apps?
Does the same thing happen for other GTK-based apps?
indeed, this does happen with some applications such as grsync, firewalld. Some graphics rendering issues (thunderbird) But not all are impacted.
I will report this on bugs.bugs
thanks
Came here to see if the bug is known already. And it is ... Thanks for opening a bug report on bugs.kde.org, @Cherkah !
Looking forward to a fix.
@BenjaminSchaaf I think this issue can be closed. We pushed a workaround for 6.3 and there's an upstream fix in GTK as well, see https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/8240.
