Jammy after logging out of wayland session and back in Chrome says it wasn't shut down correctly

[Jonathan Kamens]

In Jammy when I have Chrome running and I log out of a Wayland session and then log back in and restart Chrome it says it wasn't shut down correctly.

I'm pretty sure in earlier releases Chrome was given the opportunity to shut down cleanly when I logged out, but :shrug: I could be remembering this incorrectly.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 40.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
Uname: Linux 5.13.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu73
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov 28 11:17:25 2021
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-16 (834 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
RelatedPackageVersions: mutter-common 40.5-1ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2021-11-09 (19 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-10-16T09:30:38.992726

[Daniel van Vugt (vanvugt)]

This may be caused by gnome-shell quietly crashing on logout.

Please:

1. Uninstall these extensions: '<email address hidden>', '<email address hidden>', 'multi-volume@tigersoldier', '<email address hidden>'

2. Log in again and verify the bug still occurs.

3. If the bug does still occur then check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

[Jonathan Kamens (jik)]

I removed '<email address hidden>', '<email address hidden>', and '<email address hidden>', but GNOME doesn't seem to think I have 'multi-volume@tigersoldier' installed, so I'm not sure where you got that from or what to do with it. See attached screenshot of Extensions app. I also looked on extensions.gnome.org and it also doesn't list it as an installed extension.

With the other three extensions removed completely the problem still occurs even after two logout / login cycles after removing the extensions to ensure they're completely purged.

Regarding the crash instructions you sent, there is in fact a Chrome crash in /var/crash that looks relevant but of course I can't report it with ubuntu-bug because Chrome is not an Ubuntu package. There are no crashes on errors.ubuntu.com for my Whoopsie ID, and I've already got the workaround from bug 994921.

[Daniel van Vugt (vanvugt)]

Regarding extensions, please try:

  cd ~/.local/share/gnome-shell/
  rm -rf extensions

and then log in again.

For the crashes I was actually expecting a gnome-shell crash would cause it but a Chrome crash makes more sense. So I'm going to close this bug as a Chrome crash. You can report bugs about that to https://bugs.chromium.org/p/chromium/issues/list

[Jonathan Kamens (jik)]

1) ~/.local/share/gnome-shell/extensions is empty

2) I reproduced this issue with Chromium and there is no Chromium crash in /var/crash, nor is there an error report for Chromium tied to my whoopsie ID.

Since the chromium snap is provided by Canonical and this issue is reproducible with Chromium does that mean it's no longer an "Invalid" issue?

[Nathan Teodosio (nteodosio)]

I don't think Chromium is misbehaving here, at least not the snap, I tested with a deb I got from upstream and it's the same.

At any rate, and correct me if mistaken, when terminal emulators are terminated, they send HUP to their jobs. So when Xorg or Wayland dies, it may kill the terminal before Chromium, and then the terminal HUPs Chromium.

Now try "pkill -HUP chrom" and it will say the same thing, "didn't shut down correctly".

I consider that more as a chance for the user to easily restore his pages — Firefox does the same and I guess many users appreciate it.