Ubuntu
linux-hwe-5.8 package

[ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse

Bug #1919093 reported by Stig Berggren on 2021-03-14

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux-hwe-5.8 (Ubuntu)	New	Undecided	Unassigned
	nvidia-graphics-drivers-460 (Ubuntu)	New	High	Unassigned

Bug Description

When logging in, the screen goes purple and blank, but I can still move the mouse. Keyboard shortcuts such as Alt+F2 or Ctrl+Alt+T have no effect. I can use Ctrl+Alt+F[1345...] to switch to a shell or go back to the login screen, but Ctrl+Alt+F2 puts me back in the blank state. When turning off the computer from the login screen, I get a warning that my user is logged in.

The most similar previous bug report I've been able to find is https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1766137. However, my problem occurs regardless of whether I fail the first login attempt or not, or whether I enter my password or scan my fingerprint.

I have replicated the problem booting with two kernel versions: Linux 5.8.0-44 and Linux 5.8.0-43

I have been using the computer since November 2020, and this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13). I have previously had trouble getting getting external monitors to work, but even that has worked fine for the past few months.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Mar 14 21:19:17 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:22c0]
NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo TU117GLM [Quadro T2000 Mobile / Max-Q] [17aa:22c0]
MachineType: LENOVO 20TH000VMX
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
TERM=linux
PATH=(custom, no user)
LANG=nb_NO.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic root=UUID=9da324cb-cdc4-42f8-abdd-b764e455a1f7 ro recovery nomodeset dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/21/2020
dmi.bios.release: 1.12
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET27W (1.12 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TH000VMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.7
dmi.modalias: dmi:bvnLENOVO:bvrN2VET27W(1.12):bd12/21/2020:br1.12:efr1.7:svnLENOVO:pn20TH000VMX:pvrThinkPadP1Gen3:rvnLENOVO:rn20TH000VMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P1 Gen 3
dmi.product.name: 20TH000VMX
dmi.product.sku: LENOVO_MT_20TH_BU_Think_FM_ThinkPad P1 Gen 3
dmi.product.version: ThinkPad P1 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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

See original description

Tags:

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-14:

BootLog.txt Edit (1.9 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (86.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (24.0 KiB, text/plain; charset="utf-8")
DpkgLog.txt Edit (69.4 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (72.5 KiB, text/plain; charset="utf-8")
Lspci-vt.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (483 bytes, text/plain; charset="utf-8")
Lsusb-t.txt Edit (967 bytes, text/plain; charset="utf-8")
Lsusb-v.txt Edit (69.3 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (17.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (11.4 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (8.5 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (255.0 KiB, text/plain; charset="utf-8")
XorgLog.txt Edit (42.5 KiB, text/plain; charset="utf-8")
acpidump.txt Edit (1.4 MiB, text/plain; charset="utf-8")

description:

updated

Daniel van Vugt (vanvugt) on 2021-03-15

tags:

added: regression-update

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-15:

Thanks for the bug report. It appears the computer is in recovery/low graphics mode according to these kernel parameters "recovery nomodeset" and the Xorg log concurs in using "FBDEV". If you did that just to report this bug then that's OK, please just run this command to collect some logs of when the bug was occurring:

  journalctl -b-1 > journal1.txt
  journalctl -b-2 > journal2.txt
  journalctl -b-3 > journal3.txt

and attach the resulting text files here.

If you are not in recovery mode intentionally then please reboot, tap Esc before Ubuntu starts, and be sure to select the regular non-recovery kernel.

Separately, please install the Nvidia driver, either by the 'Additional Drivers' app or by running:

sudo apt install nvidia-driver-460

affects:	xorg (Ubuntu) → xorg-server (Ubuntu)
Changed in mutter (Ubuntu):
status:	New → Incomplete
Changed in xorg-server (Ubuntu):
status:	New → Incomplete

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

journal1.txt Edit (534.8 KiB, text/plain)

You're right, I booted in recovery mode in order to use `ubuntu-bug`. I guess I could have used TTY3 to do the same thing, but they have some serious video glitches as well - perhaps that is a separate issue.

I have now configured an SSH server on the problematic machine, so I will able to gather more info from now on even when reproducing the problem.

Please find journal[123] attached

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

journal2.txt Edit (441.2 KiB, text/plain)

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

journal3.txt Edit (582.0 KiB, text/plain)

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-15:

Thanks. journal1.txt seems to show either GNOME or Xorg failing to start but I can't tell why. The other logs are from recovery mode, so not relevant.

Please try:

1. Selecting 'Ubuntu on Wayland' from the login screen, just before you enter your password.

2. Checking for any crashes that might have occurred using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

3. Installing the Nvidia driver, either by the 'Additional Drivers' app or by:

sudo apt install nvidia-driver-460

and then reboot.

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

In the process of installing `nvidia-driver-460`, I was prompted to choose a temporary password because of UEFI secure boot. However, I was never prompted to reenter it on the subsequent reboot.

The issue persists when logging in to "Ubuntu", but not when I choose "Ubuntu with Wayland" - I'm getting a proper desktop then.

I will check for crashes using the instructions in the link.

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

There is one `.crash` file in /var/crash, but it is not relevant - it's from the MS Teams app and it also predates the problem described here.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-15:

Thanks. Please also try some older/newer kernels: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

Alternatively, if you just need a working machine then it sounds like you should uninstall the Nvidia-460 driver and stick with 'Ubuntu on Wayland'.

summary:	- Desktop does not load after login - purple screen with mouse + [ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load + after login - purple screen with mouse
Changed in mutter (Ubuntu):
status:	Incomplete → New
Changed in xorg-server (Ubuntu):
status:	Incomplete → New

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-15:

#10

Using Wayland lets me be productive for the most part, but there are some things that don't work for me on Wayland

- Chromium
- Screen sharing in Teams
- Spotify

Thanks a lot for the help so far!

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-16:

#11

> this problem occurred for the first time when I rebooted it this weekend (Sat 2021-03-13)

Please attach a copy of /var/log/apt/history.log so that we might figure out what changed around that time. I was only guessing that it's probably the kernel.

Changed in mutter (Ubuntu):
status:	New → Incomplete
Changed in xorg-server (Ubuntu):
status:	New → Incomplete

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-16:

#12

Another log like that in comment #3 might also help.

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-16:

#13

history.log Edit (13.8 KiB, text/plain)

Please find attached the apt log from this March. As mentioned, the problem first occurred on a reboot on March 13, but the computer had been on for a few days before that. I'm pretty certain it had been rebooted previously in the same month.

When you request another log like `journal1.txt`, should I reboot to recreate the error state, or would it be useful to gather the log while I'm using the computer in Wayland?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-16:

#14

A shorter log is best. So maybe reboot and then run in a VT:

journalctl -b0 > journal.txt

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-16:

#15

journal.txt Edit (467.7 KiB, text/plain)

The attached log gathered after a reboot into Ubuntu, a couple of minutes after logging in. The CPU fan is spinning up pretty frequently.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-16:

#16

That's kind of good. When the CPU fan is spinning hard, what process does 'top' report using the most CPU?

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-03-16:

#17

Please ensure you don't have any extensions enabled, by running:

gsettings set org.gnome.shell enabled-extensions "[]"
rm -rf ~/.local/share/gnome-shell/extensions

and reboot. Does the problem still occur after that?

affects:

xorg-server (Ubuntu) → gnome-shell (Ubuntu)

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-03-16:

#18

The CPU intensive process is `/usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3`, which uses close to 100% of one core continuously.

I have no extension enabled. I have checked that there is no `~/.local/share/gnome-shell/extensions` on my system, and `gsettings get org.gnome.shell enabled-extensions` returns `@as []`.

Daniel van Vugt (vanvugt) on 2021-03-17

affects:	gnome-shell (Ubuntu) → nvidia-graphics-drivers-460 (Ubuntu)
affects:	nvidia-graphics-drivers-460 (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status:	Incomplete → New
importance:	Undecided → High
no longer affects:	mutter (Ubuntu)

Revision history for this message

Stig Berggren (stigjb) wrote on 2021-04-15:

#19

Can I do anything to help troubleshoot this issue further? The issue has persisted through the last kernel updates, I am now on kernel version 5.8.0-49. Wayland works for the most part, but some apps won't start, and screen sharing works only partially.

Revision history for this message

Daniel van Vugt (vanvugt) wrote on 2021-04-15:

#20

I've seen a couple of people report issues with manual NVIDIA driver installations recently but so long as you installed the NVIDIA driver through the 'Additional Drivers' app then it is expected to work.

I think I ran out of ideas for this bug a month ago but it does seem to be assigned to the wrong project so I shall change that.

affects:

xorg-server (Ubuntu) → nvidia-graphics-drivers-460 (Ubuntu)

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux-hwe-5.8 package

[ThinkPad P1 Gen 3 w/ Intel + Nvidia Quadro T2000] Desktop does not load after login - purple screen with mouse

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux-hwe-5.8 package