User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.61 Safari/537.36
Steps to reproduce:
On Ubuntu/Jammy, using 1:91.9.1+build1-0ubuntu0.22.04.1, I'm dragging mail from the main INBOX to other (sub)folders. This works, for a couple of moves, but then Thunderbird becomes completely unresponsive and the GNOME window-is-not-responding message pops up.
Actual results:
Thunderbird deadlocks and cannot wake up. Only the Force Quit button works. After which I can restart Thunderbird and resume cleaning of my INBOX.
Expected results:
Thunderbird should just keep running so I can keep moving e-mails to different subfolders.
Basically it appears like Wayland has something to do with this.
When starting thunderbird with XDG_SESSION_TYPE=x11 WAYLAND_DISPLAY= it looks like Thunderbird behaves normally and no deadlocks occur.
One of the things that stand out, is that without Wayland enabled, the following messages are not observed on stderr anymore:
Created attachment 9280118
lp1977715.txt
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ 102.0.5005. 61 Safari/537.36
Steps to reproduce:
On Ubuntu/Jammy, using 1:91.9. 1+build1- 0ubuntu0. 22.04.1, I'm dragging mail from the main INBOX to other (sub)folders. This works, for a couple of moves, but then Thunderbird becomes completely unresponsive and the GNOME window- is-not- responding message pops up.
Actual results:
Thunderbird deadlocks and cannot wake up. Only the Force Quit button works. After which I can restart Thunderbird and resume cleaning of my INBOX.
Expected results:
Thunderbird should just keep running so I can keep moving e-mails to different subfolders.
====
Verbose explanation and debug info here: /bugs.launchpad .net/ubuntu/ +source/ thunderbird/ +bug/1977715
https:/
(also attached as lp1977715.txt )
Basically it appears like Wayland has something to do with this. TYPE=x11 WAYLAND_DISPLAY= it looks like Thunderbird behaves normally and no deadlocks occur.
When starting thunderbird with XDG_SESSION_
One of the things that stand out, is that without Wayland enabled, the following messages are not observed on stderr anymore:
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
But that may be unrelated.