gnome-shell regularly showing the "Oops! Something went wrong/ logout" screen after Alt-F2 r RET

[Jonathan Kamens]

With the most recent Mantic updates gnome-shell is regularly, but not every time, crashing and showing me the "Oops!" screen and forcing a logout when I type Alt-F2 r RET (using X11, obviously, since AFAIK that still isn't supported in Wayland).

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45~beta.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 1 09:57:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-01-02 (1703 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-05-20 (104 days ago)

[Daniel van Vugt (vanvugt)]

Seems it keeps crashing at:

[ 132.445679] jik5.kamens.us gnome-shell[5201]: GNOME Shell crashed with signal 11
[ 132.445679] jik5.kamens.us gnome-shell[5201]: == Stack trace for context 0x55f933e61270 ==
[ 132.446132] jik5.kamens.us gnome-shell[5201]: #0 55f933f7b088 i resource:///org/gnome/shell/ui/main.js:262 (2956a72e52e0 @ 12)
[ 132.446132] jik5.kamens.us gnome-shell[5201]: #1 55f933f7aff8 i resource:///org/gnome/shell/ui/init.js:21 (2956a727d060 @ 48)

which is indeed the restart function itself:

    global.display.connect('restart', () => {
        global.reexec_self();
        return true;
    });

So next we need to see a stack trace of the C code leading up to recexec_self.

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.

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.

[Daniel van Vugt (vanvugt)]

It's probably this (to be fixed in 45.rc):

https://gitlab.gnome.org/GNOME/mutter/-/issues/2852

[Jonathan Kamens (jik)]

1) Is crash reporting fixed? Ref: https://bugs.launchpad.net/launchpad/+bug/2033653

2) Do you still need the crash report given your comment above?

[Daniel van Vugt (vanvugt)]

We can just wait until 45.rc (or later) is in Ubuntu and then you'll know if it was the same issue as mutter#2852.