Opened 3 years ago
Last modified 2 years ago
#3504 new bug
delguge-gtk crash at popup elements in Wayland session
Reported by: | bvasiliev | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | not applicable |
Component: | GTK UI | Version: | develop |
Keywords: | gtk, popup, wayland | Cc: |
Description
GTK interface crashes on creating any popup elements in Wayland session.
To reproduce:
- Start deluge-gtk in Wayland session.
- Try iteract any popup, like show_move_storage_dialog: 'Move download folder' > Dropdown.
Attachments (2)
Change History (4)
by , 3 years ago
Attachment: | deluge-debug.txt added |
---|
comment:1 by , 3 years ago
Milestone: | needs verified → not applicable |
---|
This is likely to be OS/Gtk related so nothing that Deluge can specifically fix.
Create a report to whomever packages Deluge for the system you are using and link back here for cross-reference.
comment:2 by , 2 years ago
This is still coming up in 2.1.1, and it's traceable back to GTK as you said before. I've resorted to using deluged and accessing deluge via the console and the web interface. Not ideal, but it works.
The forum users are indicating that this happens on macOS, and when it does crash, it's completely unrecoverable for the average person. Deluge crashes on launch 100% of the time. macOS is throwing an exception for sandbox violations because GTK is trying to use some property in a core framework that it's not entitled to, and Metal (the GPU acceleration libraries) are barking in the logs. There's no obvious way to recover and restore normal functionality once this crash occurs.
Bottom line: your users will assume the bug is in deluge, not in GTK, because they don't know any better.
If this were my app, I'd treat the bug as a showstopper and figure it out.
Since you (cas) and ibizaman are the ones integrating GTK for the user interface, don't you think it's your responsibility to file a bug with the GTK team instead of making your users do it?
debug log