[nvidia] gnome crashes after running `apt upgrade`

Bug #1915481 reported by Walt Mankowski on 2021-02-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Undecided
Unassigned
nvidia-graphics-drivers-460 (Ubuntu)
Undecided
Unassigned

Bug Description

This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1)

When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2)

When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't.

Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK.

I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.14
ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 11 20:27:58 2021
InstallationDate: Installed on 2016-12-27 (1507 days ago)
InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

Walt Mankowski (waltman) wrote :
Walt Mankowski (waltman) wrote :

On second thought, a better title would be "gnome crashes WHILE running apt upgrade" because it always happens while it's in the middle of installing the new packages.

Chris Guiver (guiverc) on 2021-02-12
affects: ubuntu → gnome-shell (Ubuntu)
Daniel van Vugt (vanvugt) wrote :

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.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Walt Mankowski (waltman) wrote :

Thanks for replying so quickly. Unfortunately step 1 didn't show any crash reports.

Step 2 doesn't show anything recent, but there were crashes on January 6 that might be relevant. They are:

gnome-control-center: https://errors.ubuntu.com/oops/28c05820-501b-11eb-9503-fa163e983629
gnome-shell: https://errors.ubuntu.com/oops/16d604a2-501b-11eb-8b96-fa163e6cac46

Just to be clear, is the workaround from step 3 simply "comment out line 23 from /etc/apport/crashdb.conf and reboot"? There are a lot of other suggestion in that bug report and I wanted to doublecheck that that's all I need to do.

As for reproducing the crash, it's probably impossible to exactly reproduce it since it only happens when I'm running `apt upgrade` to install new packages, and these particular new packages have already been upgraded. The best I can do is make the change, reboot, and wait for it to happen again with some new set of packages.

Daniel van Vugt (vanvugt) wrote :

Your gnome-shell crash from January 6 is bug 1897765, which should be fixed by gnome-shell v3.38.2 in theory. There is however some evidence now that it's not fully fixed...

You can ignore step 3 above. More useful for bugs like 1897765 would be to:

1. Reproduce the crash again.

2. If you can log in again then run:

   journalctl -b0 > journal.txt

3. If you had to reboot then log in and run:

   journalctl -b-1 > prevjournal.txt

4. Attach the resulting text file here.

Walt Mankowski (waltman) wrote :

Reproducing the crash exactly is basically impossible -- I have no idea what I was doing to trigger it on January 6. The crashes I've been experiencing happen seemingly at random while running `apt update`. It may well happen again in the future, but based on past experiences it will be with a different set of packages than the last time.

Also gnome-shell was updated on January 20, and the crashes have continued to happen since then. But the last time I rebooted was after a crash, so I just ran `journalctl -b-1 > prevjournal.txt` and I've attached the results.

Walt Mankowski (waltman) wrote :

Out from running

journalctl -b-1 > prevjournal.txt

Walt Mankowski (waltman) wrote :

I believe the crash happened at roughly Feb 11 19:42:41.

Daniel van Vugt (vanvugt) wrote :

It looks like there aren't any crashes coming from gnome-shell directly, but gnome-shell is dying because it depends on Xorg which is failing.

Feb 11 19:43:07 scruffy gnome-shell[9580]: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.

Feb 11 19:43:31 scruffy gnome-shell[75980]: gnome-shell: Fatal IO error 0 (Success) on X server :0.

summary: - gnome crashes after running `apt upgrade`
+ [nvidia] gnome crashes
Changed in gnome-shell (Ubuntu):
status: Incomplete → New

Alternatively, if the problem happened at "Feb 11 19:42:41" as you say then it might be the result of systemd reloading... something...

Feb 11 19:42:41 scruffy dbus-daemon[1908]: [system] Reloaded configuration
Feb 11 19:42:41 scruffy dbus-daemon[1908]: [system] Reloaded configuration
Feb 11 19:42:41 scruffy dbus-daemon[1908]: [system] Reloaded configuration
Feb 11 19:42:41 scruffy systemd[1]: Reloading.

summary: - [nvidia] gnome crashes
+ [nvidia] gnome crashes after running `apt upgrade`
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers