[Users] [Bug 4417] New: Notification plugin load triggers segfault on wayland if global hotkey is enabled

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Thu Dec 3 20:22:58 CET 2020


https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4417

            Bug ID: 4417
           Summary: Notification plugin load triggers segfault on wayland
                    if global hotkey is enabled
           Product: Claws Mail (GTK3)
           Version: GIT
          Hardware: PC
                OS: Windows 10
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Plugins/Notification
          Assignee: users at lists.claws-mail.org
          Reporter: 1i5t5.duncan at cox.net

At commit 4752d6922.  Running on wayland.  Upgrade issue with the notification
plugin on a switch from claws/gtk2 3.17.8 on X.

My old gtk2/X claws installation had long had the notification plugin global
hotkey enabled.  When I switched to live-git-gtk3-native-wayland claws, all the
loaded plugins unregistered and I had to load plugins again.  While my other
previous plugins loaded fine, attempting to load the notification plugin was
segfaulting claws and sometimes (not always) taking kde/plasma/wayland (which
like claws isn't entirely stable on wayland yet) with it.  Syslog said the
segfault was in libX11.

After a bit of googling (on duckduck, FWIW) I found the GDK_BACKEND=x11 method
to force claws/gtk3 to run in X mode on wayland, which allowed a successful
load of the notification plugin.  After loading the plugin in X mode I was able
to disable the global hotkeys in the notification plugin config and quit.

I could then run claws in wayland mode with the notification plugin enabled.


So the notification plugin, global-hotkeys module, needs to check that it's
running in X mode before attempting to register the hotkey on X.  Because if
it's in wayland mode it's at best not going to work, and could well trigger a
segfault, as it was doing for me.

Unfortunately I'm not a dev so I can't provide a proper patch, but I can at
least hope with that level of specificity it's reproducible and will be an easy
fix for those who do have that skill.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Users mailing list