-
Notifications
You must be signed in to change notification settings - Fork 341
GTK Dropdown Menu Crashes GTK Program #2032
Comments
Your bug report is missing debug logs and your config file. Please add a link to the full debug log file and the config. Can you run the app with |
@emersion Updated original post with the output from both of those. Edit: |
The height is too big. |
Can I do anything to assist further? |
It would be interesting to try to see where this big value is coming from in wlroots. |
Getting the same issue as @distek too |
So this doesn't occur on any other device that I have, one of which is also running nouveau, and two that's on Intel integrated. I assume that I have, at some point in the past, screwed something up related to this on this particular work station. @isabelomakhanya , if you're still having this issue, update here and I can leave it open. Otherwise, I'll close it in about a week. |
I can't reproduce this with Edit: I have managed to reproduce the crash reliably again. When I floated the glade window, I've noticed that for some reason it ended up bigger than my screen. Once I shrank it down to a reasonable size, clicking on an element of the GtkMenuBar crashes glade every time. But, now that I have found a reliable test, I have also tested it in Weston.. And glade has crashed there, too. Therefore, this is either a bug in the Wayland libraries, a bug in GTK 3, or just a bug in glade. |
@FreeFull Have you tested in other stand-alone GTK programs? |
|
Quick update on this: gucharmap seems to now be native wayland and thus works as expected. |
Could it be a bug in gucharmap; For me it used to crash, but currently it doesn't - the fonts drop-down menu appears as a black rectangle from the top to the bottom of the screen, and the following appears in the sway log: 00:09:30.502 [ERROR] [GLES2] GL_INVALID_VALUE in glTexImage2D(invalid width=293 or height=27868 or depth=1) Although I can't see the font names, clicking on the rectangle selects an entry so the underlying drop down does work. I tried running it under KDE (plasma-wayland) with WAYLAND_DEBUG=1, where it worked correctly, as well as under sway, and I'm attaching the two logs here - in both I clicked to activate the drop down, clicked on a random entry, and then closed the program from the "File" menu: Under plasma, it does |
I had the same issue with DBeaver 21.2.2 on ArchLinux. With On the application side the error is the following:
The fix for me was setting |
I had the same with Firefox (93.0.1) today on arch. (wlroots 0.14.1-2 and sway 1:1.6.1-2)
|
Hello
Encountering an issue with GTK drop down menus in Sway specifically(haven't tried other wlroots based WMs/compositors). Raising this issue here as it doesn't appear to be tracked after the close of this issue from Sway:
swaywm/sway#1577
When clicking the menu in
gucharmap
for example:This is the only output I get from the app.
Only thing I could find in sway.log:
Works fine in X.
I do know from using it in X, the drop down extends past the window border. I'm assuming this is related to the "Cairo image surface"
In the referenced issue, it's stated that it will be fixed by wlroots, but that was about two years ago. Is this an abandoned/wontfix issue?
It's not imperative to my use of Sway/Wayland, just a nicety.
Possibly relevant env variables:
Sway config snippet:
Let me know if you need anything else.
Thanks for all the work on this, it's been an amazing experience thus far.
sway --debug 2> sway.log
:http://ix.io/2c8K
WAYLAND_DEBUG=1 gucharmap &> gucharmap.log
:http://ix.io/2c8L
config:
http://ix.io/2c8P
wlroots has migrated to gitlab.freedesktop.org. This issue has been moved to:
https://gitlab.freedesktop.org/wlroots/wlroots/-/issues/2032
The text was updated successfully, but these errors were encountered: