[nvidia] xorg via gdm-x-session fails to start with "Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices"

[René Walendy]

After performing apt dist-upgrade and rebooting, plymouth doesn't run in full resolution and the graphical session won't start. The system is stuck on a blinking cursor. A full log file is attached. Here is the error:

Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 0 deleted because of no matching config section.
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "modesetting"
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section.
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "fbdev"
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadSubModule: "fbdevhw"
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (EE) Screen 1 deleted because of no matching config section.
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (II) UnloadModule: "vesa"
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (EE)
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: Fatal server error:
Mär 03 13:04:13 xxxx /usr/lib/gdm3/gdm-x-session[1753]: (EE) Cannot run in framebuffer mode. Please specify busIDs for all framebuffer devices

Interestingly, pressing Ctrl+Alt+F1 when the system is stuck successfully starts the XServer and brings up the login screen. While I experience some font rendering issues, most things seem to work fine after that.

lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

uname -a
Linux xxxx 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

The system is a Dell G5 15 5590 laptop using dual intel/nvidia rtx graphics:

lshw -c video
  *-display
       Beschreibung: VGA compatible controller
       Produkt: TU106M [GeForce RTX 2060 Mobile]
       Hersteller: NVIDIA Corporation
       Physische ID: 0
       Bus-Informationen: pci@0000:01:00.0
       Version: a1
       Breite: 64 bits
       Takt: 33MHz
       Fähigkeiten: pm msi pciexpress vga_controller bus_master cap_list rom
       Konfiguration: driver=nvidia latency=0
       Ressourcen: irq:165 memory:ec000000-ecffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:4000(Größe=128) memory:ed000000-ed07ffff
  *-display
       Beschreibung: VGA compatible controller
       Produkt: UHD Graphics 630 (Mobile)
       Hersteller: Intel Corporation
       Physische ID: 2
       Bus-Informationen: pci@0000:00:02.0
       Version: 00
       Breite: 64 bits
       Takt: 33MHz
       Fähigkeiten: pciexpress msi pm vga_controller bus_master cap_list rom
       Konfiguration: driver=i915 latency=0
       Ressourcen: irq:152 memory:eb000000-ebffffff memory:80000000-8fffffff ioport:5000(Größe=64) memory:c0000-dffff

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1865870

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[René Walendy (0k53-rene-f830)]

I don't have nvidia-graphics-drivers-440, so I can't run apport on it.
The graphics drivers are as they were when I installed the system, I did not make any manual changes apart from regularly running apt upgrade. This system is not using the graphics-drivers PPA.

dpkg -l | grep nvidia | cut -c -63
ii hashcat-nvidia 20180828+nmu1
ii libnvidia-cfg1-440:amd64 440.59-0ubuntu2
ii libnvidia-common-440 440.59-0ubuntu2
ii libnvidia-compute-440:amd64 440.59-0ubuntu2
ii libnvidia-compute-440:i386 440.59-0ubuntu2
ii libnvidia-decode-440:amd64 440.59-0ubuntu2
ii libnvidia-decode-440:i386 440.59-0ubuntu2
ii libnvidia-encode-440:amd64 440.59-0ubuntu2
ii libnvidia-encode-440:i386 440.59-0ubuntu2
ii libnvidia-fbc1-440:amd64 440.59-0ubuntu2
ii libnvidia-fbc1-440:i386 440.59-0ubuntu2
ii libnvidia-gl-440:amd64 440.59-0ubuntu2
ii libnvidia-gl-440:i386 440.59-0ubuntu2
ii libnvidia-ifr1-440:amd64 440.59-0ubuntu2
ii libnvidia-ifr1-440:i386 440.59-0ubuntu2
ii nvidia-compute-utils-440 440.59-0ubuntu2
ii nvidia-dkms-440 440.59-0ubuntu2
ii nvidia-driver-440 440.59-0ubuntu2
ii nvidia-kernel-common-440 440.59-0ubuntu2
ii nvidia-kernel-source-440 440.59-0ubuntu2
ii nvidia-prime 0.8.14
ii nvidia-settings 440.44-0ubuntu1
ii nvidia-utils-440 440.59-0ubuntu2
ii screen-resolution-extra 0.18build1
ii xserver-xorg-video-nvidia-440 440.59-0ubuntu2

[Daniel van Vugt (vanvugt)]

Please then run:

  journalctl -b0 > journal.txt

and attach the resulting file.

[René Walendy (0k53-rene-f830)]

Thanks for the quick reply! Here you go.
(I've masked some identifiable information about our network but I did not remove any lines from the log)

[Daniel van Vugt (vanvugt)]

Interesting, thanks. I would have thought this was Nvidia-specific but bug 1849545 sounds similar and has no Nvidia at all.

[Dan Kegel (dank)]

I saw this on an ubuntu 20.04 alpha system when I did 'ubuntu-drivers install' to
get drivers for my gtx 1080. Reinstalling ubuntu 20.04 final made the problem vanish
(whew).

[René Walendy (0k53-rene-f830)]

I have the impression that this bug was caused by a broken plymouth update. After updating plymouth to the newest version, the issue went away and I didn't have any problems ever since.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bentsi (magidovich)]

Re-installing Plymouth didn't help