gnome-shell crash

[Joe Barnett]

gnome shell crashed when switching workspaces to check out the new 'activities' workspace indicator functionality. it also crashed when starting ms teams, not sure if that's the same bug?

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Sep 26 11:28:15 2023
DisplayManager: gdm3
InstallationDate: Installed on 2019-08-17 (1502 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
RelatedPackageVersions: mutter-common 45.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-09-26 (0 days ago)

[Daniel van Vugt (vanvugt)]

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. Run these commands:
    journalctl -b0 > journal.txt
    journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. 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.

3. If step 2 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.

[Joe Barnett (thejoe)]

-b 0

[Joe Barnett (thejoe)]

-b -1

[Joe Barnett (thejoe)]

there's nothing in /var/crash or in errors.ubuntu.com

[Daniel van Vugt (vanvugt)]

I can see three bugs there:

1. "bijiben-shell-s... segfault" -> bug 2012985

2. "<email address hidden>: Main process exited, code=killed, status=9/KILL" -> bug 2034619

3. "Cursor update failed: drmModeAtomicCommit: Invalid argument" though the shell kept running for hours after that so it wasn't fatal.

I think most likely #2 is the main problem here.