desktop freezes when changing thundebird win decorations

[motang]

I noticed a bug. In Thunderbird (deb or snap) version open and right click on the tab bar and choose customization and mess around with showing title or not and close out of it the icon for TB is still in the dock. If you click on the icon it locks up the UI.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thunderbird 1:78.3.2+build1-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
Uname: Linux 5.8.0-26-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: mram 2160 F.... pulseaudio
 /dev/snd/controlC0: mram 2160 F.... pulseaudio
BuildID: 20201006011220
CasperMD5CheckResult: skip
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 4 18:55:14 2020
DefaultProfileExtensions: extensions.sqlite corrupt or missing
DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
DefaultProfileLocales: extensions.sqlite corrupt or missing
DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732
DefaultProfilePrefSources: prefs.js
DefaultProfileThemes: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
InstallationDate: Installed on 2020-10-04 (31 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930)
IpRoute:
 default via 192.168.1.1 dev eno1 proto dhcp metric 100
 169.254.0.0/16 dev eno1 scope link metric 1000
 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.45 metric 100
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Profile1Extensions: extensions.sqlite corrupt or missing
Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite)
Profile1Locales: extensions.sqlite corrupt or missing
Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732
Profile1PrefSources: prefs.js
Profile1Themes: extensions.sqlite corrupt or missing
Profiles:
 Profile1 - LastVersion=78.0/20200629202523 (Out of date)
 Profile0 (Default) - LastVersion=78.3.2/20201006011220
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2012
dmi.bios.release: 4.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: AGH6120H.86A.0015.2012.0926.1822
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61AGL
dmi.board.vendor: Intel Corporation
dmi.board.version: G71256-202
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: sabc1
dmi.modalias: dmi:bvnIntelCorp.:bvrAGH6120H.86A.0015.2012.0926.1822:bd09/26/2012:br4.6:svnSystem76,Inc.:pnSableComplete:pvrsabc1:rvnIntelCorporation:rnDH61AGL:rvrG71256-202:cvnSystem76,Inc.:ct3:cvrsabc1:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Sable Complete
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: sabc1
dmi.sys.vendor: System76, Inc.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you give exact steps, when you say 'mess around with showing title or not', does it mean that if you open that dialog, click the box one, close thunderbird you get the issue? or you need more clicks?

does it do every time?

could you do
$ journalctl -f
trigger the issue and see what is printed on the journal log?

[motang (mohan-ram)]

Hello,

These are the steps to reproduce it for both .deb and snap versions.
Once Thunderbird is open, right click around the tab bar and choose customize. Once in that window, choose either to show title bar or hide (depending on what you have already done prior). Close the customize window, but you will notice there are two dots beside Thunderbird icon on Ubuntu dock indicating it has two windows open. If you click on Thunderbird the UI locks. If you by chance do not click on the icon on Ubuntu dock you can clear off the extra dot by restarted GNOME UI by typing 'r' in run dialog for x.org. Not sure if this is reproduceable under Wayland.

[Sebastien Bacher (seb128)]

Could you add the 'journalctl -b 0' log from the system after getting the issue? Reassigning to gnome-shell since that's where the lock is (could be due to the dock extension though)

[motang (mohan-ram)]

How do I add that w/o having to submit a new bug?

[Daniel van Vugt (vanvugt)]

After the freeze happens next, please wait 10 seconds, reboot and then run:

  journalctl -b-1 > prevboot.txt
  gsettings list-recursively org.gnome.shell > settings.txt

and attach the resulting text files here.

[Daniel van Vugt (vanvugt)]

Also...

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[motang (mohan-ram)]

Okay I have created the bug again and here are the requested files.

[motang (mohan-ram)]

Second file.

[Daniel van Vugt (vanvugt)]

Thanks. The only relevant information I can find in there is:

Nov 06 05:44:28 Sable-Complete gnome-shell[18366]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1871262, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[motang (mohan-ram)]

Thanks I will take a look at the other bug and will mark as effecting me and add any additional info that I can.