Mastodawn

Ludovic Courtès Sep 12, 2025

I found a sure way to crash #EXWM + #Emacs: ‘M-x debbugs-gnu’.

Apparently that spawns a thread, then EXWM starts complaining about handling XCB events from the wrong thread (couldn’t capture the exact message), and usually seconds later Emacs crashes.

Anyone else seen that? (On #Guix I guess.)

Show thread

Zack Weinberg Sep 12, 2025

@civodul I haven't seen this myself but I wonder if it's related to the ancient slap-fight between Emacs and GTK over how X connections are supposed to work. Can you conveniently try an Xaw build of Emacs?

(see https://gitlab.gnome.org/GNOME/gtk/-/issues/221 and https://gitlab.gnome.org/GNOME/gtk/-/issues/2315 )

Closing displays (#221) · Issues · GNOME / gtk · GitLab

Submitted by Owen Taylor Link to original bug (#85715)

GitLab

Show thread

zrzz

@zwol @civodul No crash for me and I get results with M-x debbugs-gnu-show-last-result. EXWM remained responsive but as I was switching buffer during the query once I got "Error running timer `exwm-input--update-focus-commit': (error "Attempt to accept output from process XELB locked to thread #")" in the messages buffer.

I build my Emacs with toolkits disabled (--without-x-toolkit). debbugs-gnu-use-threads is t.