Desktop won't get to gdm after graphics driver update

[Oliver Smith]

After a graphics driver update my desktop would not progress past the boot splash screen and hangs on a blinking cursor.

Ubuntu recovery mode options and dpkg rebuilds did not resolve the issue.

I ended up being able to get to the desktop session by using "nomodeset" but only had access to one monitor.

After consulting with the desktop team the issue was an incomplete kernel module rebuild and was resolved with the following command:

`sudo apt install --reinstall nvidia-dkms-535`

However this is not intuitive to users as a solution and needs to be further investigated in terms of finding a more robust update path for NVIDIA machines to avoid this situation occurring. Looking online it seems like a common problem, with a variety of non-relevant proposed solutions on Ask Ubuntu.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-535 535.113.01-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-33-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 29 09:48:42 2023
InstallationDate: Installed on 2023-03-06 (206 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223)
SourcePackage: nvidia-graphics-drivers-535
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

The way this is worded is still a duplicate of bug 1975650.

I think Seb was suggesting logging a bug about the specific errors in your DKMS build log.

[Dimitri John Ledkov (xnox)]

You are building driver from source......

...... instead of using we prebuilt for you?

Have you considered removing them all, and installing them with `Additional Drivers` GUI such that you only run the one we already prebuilt for you, and signed.

Are you running the system without secureboot? Or pointlessly building dkms module which refuses to load?
Or did you enroll an unsecured Mok key on your system?

I want to know how to you got to the place where you are not using LRM (prebuilt) drivers, and ended up installing dkms package (which we publish as proof that one can built id stand-alone and how our prebuilt drivers are precreated)

[Daniel van Vugt (vanvugt)]

`sudo apt install --reinstall nvidia-dkms-535` was the fix, not the bug.

I'm pretty sure Oliver was using the default Additional Drivers and they stopped working. Just like bug 1975650.

[Launchpad Janitor (janitor)]

[Expired for nvidia-graphics-drivers-535 (Ubuntu) because there has been no activity for 60 days.]