Skip to content

Thunderbird crashes with the octopus "Lost connection to Wayland compositor."

I'm running Thunderbird 1:115.9.0-1+b1 on debian, using Sway as a Wayland compositor with no XWayland.

I find that when Thunderbird's GUI stalls out for a while, i see this report on stderr, and then the application exits with error 1:

Gdk-Message: 19:35:16.213: Lost connection to Wayland compositor.

With the octopus (libsequoia-octopus-librnp 1.8.1-2), and a fairly large OpenPGP keyring (a few thousand keys), i regularly see UI/UX hangs of several seconds.

A similar bugzilla report about "Lost connection to Wayland compositor" suggests:

a common issue with programs ignoring GUI needs while working on some other task,

Is it possible that Thunderbird with the Octopus is more unstable in this configuration due to lengthier delays?

That bugzilla report is ostensibly closed in Thunderbird 123 using some sort of Wayland Proxy, i think on the theory that GTK3 won't complain as long as the proxy is responsive. But (a) it's not straightforward for me to install Thunderbird 123 right now and (b) if the real problem is related to delays in what passes for librnp (so that it looks like even the proxy is unresponsive because the GTK3 main loop is starved by a blocking library call), i don't see how a Wayland Proxy will actually address the issue.