Restarting GNOME doesn't work

[Connor Nolan]

Triggering a restart through Alt-F2 then "r" causes GNOME to hang for a few seconds before going to the "something went wrong" screen prompting the user to log out. But once you log out and back in, the system still has issues, with application now taking far longer to launch. This is ultimately resolved by a full system restart.

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 23 14:56:37 2023
DisplayManager: gdm3
InstallationDate: Installed on 2023-08-02 (53 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
RelatedPackageVersions: mutter-common 45.0-2ubuntu1
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to mantic on 2023-09-23 (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.

[Daniel van Vugt (vanvugt)]

Although it may have been:
https://gitlab.gnome.org/GNOME/mutter/-/issues/2977

[Connor Nolan (thebrokenrail)]

Here's the system logs, the restart occurred at 22:34 on Sep 27.

[Daniel van Vugt (vanvugt)]

Please follow steps 2 and 3 in comment #2.

[Daniel van Vugt (vanvugt)]

Please also try deleting locally installed extensions:

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

and then reboot.

[Connor Nolan (thebrokenrail)]

Steps 2 and 3 aren't possible considering the there isn't a GNOME crash in /var/crash and there isn't one listed on https://errors.ubuntu.com either.

[Daniel van Vugt (vanvugt)]

Yes error reporting was broken until recently (bug 2038650) so please check that you have that fix too (apport >= 2.27.0-0ubuntu5).

[Connor Nolan (thebrokenrail)]

I just checked, I have apport 2.27.0-0ubuntu5.

[kenjo (ken-kenjo)]

So I have this every time. alt f2 r gives me the "something went wrong"

If I do this without any opened windows on the desktop I do not get the error but just one opened window is enough to get it.

I do not get a crash in /var/crash

[kenjo (ken-kenjo)]

this is what happens if I have a window when doing the restart