Black screen on login when using the proprietary nvidia-drivers

[Mike Gresens]

1)

upgrade ubuntu from 18.04 to 20.04
->
login crash loop

2)

sudo apt-get purge nvidia*
->
no login crash loop (because using nouveau driver as fallback)

3)

sudo apt install nvidia-driver <xyz>
->
login crash loop (same for 390, 435, 440)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu24
Architecture: amd64
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2018-04-27 (711 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
NonfreeKernelModules: nvidia_modeset nvidia
Package: nvidia-driver-440 440.64-0ubuntu3
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29
Tags: focal third-party-packages
Uname: Linux 5.4.0-23-generic x86_64
UpgradeStatus: Upgraded to focal on 2020-04-05 (2 days ago)
UserGroups: adm cdrom dip docker kvm lpadmin microk8s plugdev sambashare sudo
_MarkForUpload: True

[Mike Gresens (msg-72)]

I don't know whether ubuntu was uploading crash-reports or not.

For all crashes in /var/crash I found a "...1000.uploaded" file.

[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 1871169

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.

[Mike Gresens (msg-72)]

1)

I installed nvidia driver 440 from "additional drivers" again (via ui).
reboot.
after login black screen. monitor power mode.

2)

'apport-collect 1871169'
->
Package nvidia-graphics-drivers-440 not installed and no hook available, ignoring

*** Problembericht wird aktualisiert

Keine zusätzlichen Informationen gesammelt.

Bitte eine Taste drücken, um fortzufahren …
Keine aktuellen Absturzberichte. Versuchen Sie --help für weitere Informationen.

3)

that is installed:

Auflistung...
nvidia-driver-440/focal,now 440.64-0ubuntu3 amd64 [installiert]

4)

don't know at all...
"nvidia-graphics-drivers-440 not installed"
and
"nvidia-driver-440/focal,now 440.64-0ubuntu3 amd64 [installiert]"

why 'nvidia-graphics-drivers-440' and 'nvidia-driver-440' ???

all confusing. and not working

[Mike Gresens (msg-72)]

this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1870779

[Mike Gresens (msg-72)]

i am using two 4k monitors @ 60 hz connected by DPs.
currently scaling @ 200% (would like 175% if fs works).

[Mike Gresens (msg-72)]

... and a nvidia gtx 1080 card.

[Daniel van Vugt (vanvugt)]

Sorry you're running into problems with apport-collect...

Please try this:

  apport-cli -p nvidia-driver-440 -u 1871169

and if that didn't work then try:

  ubuntu-bug nvidia-driver-440 --save=here

and attach the file 'here' to this bug.

[Mike Gresens (msg-72)]

apport information

[Mike Gresens (msg-72)]

apport information

[Mike Gresens (msg-72)]

apport information

[Daniel van Vugt (vanvugt)]

Thanks.

Does the system work at scale 100%? I am wondering if this is bug 1870758.

Also, you seem to have quite a few OS modifications ([origin: unknown]) in https://launchpadlibrarian.net/473536084/Dependencies.txt though I am not sure that's a problem here...

[Daniel van Vugt (vanvugt)]

If the problem is not bug 1870758 then next please attach the files from:

  ~/.local/share/xorg/*

[Mike Gresens (msg-72)]

I tried the scale=1 hack in ~/config/monitors.xml - no success.

[Mike Gresens (msg-72)]

I am not sure about the "[origin: unknown]" dependencies.
Does "[origin: unknown]" packages come from 'focal-proposed' (via developer options)?!

[Daniel van Vugt (vanvugt)]

Those Xorg logs seem to all show open source drivers in use and never the proprietary Nvidia driver that this bug is about.

Please reinstall it, reproduce the bug, and then attach fresh log files.

[Daniel van Vugt (vanvugt)]

Also in case there is a crash somewhere please follow these instructions:

---

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.

[Mike Gresens (msg-72)]

"Please reinstall it, reproduce the bug, and then attach fresh log files."

okay, here is my test-procedure

1) i start with nouveau (so i have ui)
2) sudo ubuntu-drivers autoinstall
3) sudo reboot now
4) login -> black screen
5) open terminal, copy requested files
6) sudo apt-get purge nvidia*
7) sudo apt autoremove
8) sudo reboot now
9) with nouveau again i have ui to send you the copied files

did i miss something?

[Mike Gresens (msg-72)]

mike@workstation:~$ ll /var/crash/
insgesamt 87440
drwxrwsrwt 2 root whoopsie 4096 Apr 7 17:04 ./
drwxr-xr-x 14 root root 4096 Apr 26 2018 ../
-rw-r----- 1 mike whoopsie 4053586 Apr 6 18:07 _opt_Citrix_ICAClient_rtme_RTMediaEngineSRV.1000.crash
-rw-r--r-- 1 mike whoopsie 0 Apr 6 14:26 _opt_Citrix_ICAClient_rtme_RTMediaEngineSRV.1000.upload
-rw------- 1 whoopsie whoopsie 37 Apr 6 16:26 _opt_Citrix_ICAClient_rtme_RTMediaEngineSRV.1000.uploaded
-rw-r----- 1 mike whoopsie 85080358 Apr 7 10:21 _opt_Rambox_rambox.1000.crash
-rw-r--r-- 1 mike whoopsie 0 Apr 7 10:21 _opt_Rambox_rambox.1000.upload
-rw------- 1 whoopsie whoopsie 37 Apr 7 10:21 _opt_Rambox_rambox.1000.uploaded
-rw-r----- 1 mike whoopsie 276736 Apr 6 18:24 _usr_bin_software-properties-gtk.1000.crash
-rw-r--r-- 1 mike whoopsie 0 Apr 6 18:24 _usr_bin_software-properties-gtk.1000.upload
-rw------- 1 whoopsie whoopsie 37 Apr 6 18:24 _usr_bin_software-properties-gtk.1000.uploaded
-rw-r----- 1 mike whoopsie 90387 Apr 7 17:04 _usr_bin_update-manager.1000.crash
-rw-r--r-- 1 mike whoopsie 0 Apr 7 10:22 _usr_bin_update-manager.1000.upload
-rw------- 1 whoopsie whoopsie 37 Apr 7 10:22 _usr_bin_update-manager.1000.uploaded
mike@workstation:~$

all uploaded. no new crashes from today...

[Mike Gresens (msg-72)]

I tried again to collect the xorg logs.
To force new log files i did "rm .local/share/xorg/*" before booting with nvidia.

after reboot i did not find any files in ".local/share/xorg" !!
nevertheless i found xorg logs in "/var/log"

so i will attach these files now.

[Daniel van Vugt (vanvugt)]

Thanks. Indeed those new logs show the Nvidia driver version 440 in use and do not seem to report any problems with it...

Next please:

1. Run:

   gsettings list-recursively > settings.txt

   and attach the resulting file here.

2. Follow all the steps in comment #20.

[Daniel van Vugt (vanvugt)]

Actually your monitors.xml in comment #14 suggests bug 1869750. Please try:

1. Log out of all graphical sessions.

2. Ctrl+Alt+F4 and log into a text console.

3. Edit ~/.config/monitors.xml and change:

   <scale>2</scale>

   to

   <scale>1</scale>

4. Ctrl+Alt+F1 and log in again.

[Mike Gresens (msg-72)]

i am not sure if gsettings is affected from gfx-driver.
so i executed the command while using nouveau.

[Mike Gresens (msg-72)]

And i try the scale=1 hack in ~/config/monitors.xml every time i boot with nvidia - no success.

[Daniel van Vugt (vanvugt)]

I'm not sure we fully understand bug 1869750 yet. I'd say wait until that bug is declared Fix Released and then reassess if this bug is still happening.

[Mike Gresens (msg-72)]

okay, i will wait and watch that bug. thanks!

[Mike Gresens (msg-72)]

upgrading to mutter 3.36.1 fixed this bug too. good job!

[Mike Gresens (msg-72)]

nevertheless...
enabling fractional scaling and applying "175%" immediately causes black screens again.