[nvidia] Black screen (wrong VT) upon login

[Aakash]

OS: Fresh install of ubuntu 20.04

Steps:

1. Enter password to login (Black screen is shown)

Workaround:

2. After blank screen is shown, press Ctrl+Alt+F3. (It'll show terminal with login prompt)
3. Don't login, simply press Ctrl+Alt+F2. (Now desktop is shown, black screen is gone)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus.0000.01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0000:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 15 14:08:29 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. GP106 [GeForce GTX 1060 3GB] [19da:2438]
InstallationDate: Installed on 2020-04-28 (16 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2a627b38-a2bd-4bec-9551-703eab56e5da ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0801
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-K
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH61M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

Although the workaround is simple, this is a pretty serious bug for users who don't figure it out.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you add your 'journalctl -b 0' log after triggering the issue?

It would also be useful to get a log with debug enabled in /etc/gdm3/custom.conf

[Aakash (aakashubuntuu)]

With debug enabled, I restarted the computer and followed the same steps with workaround. Attached logs.

[Sebastien Bacher (seb128)]

Thanks, the log has

gdm-launch-environment][807]: GdmSessionWorker: couldn't finalize jump to VT 1: Interrupted system call

unsure what is creating the problem exactly though

[Mike Ripley (ripleymj)]

Apologies if this is completely irrelevant, but I've also started experiencing a black screen after login on Focal. This is in a VirtualBox VM using the VMSVGA driver, so absolutely no Nvidia involvement (Intel HD4600 on the host). After setting the GDM debug option, I also see the failure to jump error message.

I mostly just wanted to add this as another data point... I have kernels 5.4.0-26, 5.4.0-29, and 5.4.0-31 installed. The system boots to a desktop fine with -26 and fails with -29 and -31, and this has persisted through the VirtualBox 6.1.6 to 6.1.8 upgrade, and all other packages have stayed up to date. Can anyone else confirm if they see the same behavior with an older kernel?

[Daniel van Vugt (vanvugt)]

Mike,

That would probably be a different bug. Maybe bug 1861609. Regardless, please open a new bug so we can investigate.

[Mike Ripley (ripleymj)]

Thanks for not getting dragged down in my stupidity. I spent some more time on this, and haven't figured out how I did something so dumb, but I was missing vmwgfx.ko because I was missing the linux-modules-extras package for -29 and -31. With that in place, all's well. Sorry for the noise, just wanted to close the loop.

[Luis Alvarado (luisalvarado)]

Would this mean, this is solved now and can be closed?

[Daniel van Vugt (vanvugt)]

Indeed it's been years since I remember seeing this bug. It might have been fixed when the Nvidia drivers switched over to using KMS by default.

Let's leave it incomplete and if there are no more comments after 2 months then the bug will close automatically.

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]