purple screen after login using fingerprint

[Johannes Zeiser]

I updated the machine yesterday, and additionally added the fingerprint to pam using pam-auth-update. The screen now stays purple after logging in using the finger, but works fine after logging in using the password.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 19 21:37:43 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 470.103.01, 5.13.0-28-generic, x86_64: installed
 nvidia, 470.103.01, 5.13.0-35-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:2294]
InstallationDate: Installed on 2020-12-10 (464 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: LENOVO 20NN002NGE
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=2bcb2bd8-2364-4f28-9085-f6c366d45c6d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2021
dmi.bios.release: 1.89
dmi.bios.vendor: LENOVO
dmi.bios.version: N2LET89W (1.89 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NN002NGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.20
dmi.modalias: dmi:bvnLENOVO:bvrN2LET89W(1.89):bd11/24/2021:br1.89:efr1.20:svnLENOVO:pn20NN002NGE:pvrThinkPadX390Yoga:rvnLENOVO:rn20NN002NGE:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20NN_BU_Think_FM_ThinkPadX390Yoga:
dmi.product.family: ThinkPad X390 Yoga
dmi.product.name: 20NN002NGE
dmi.product.sku: LENOVO_MT_20NN_BU_Think_FM_ThinkPad X390 Yoga
dmi.product.version: ThinkPad X390 Yoga
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
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)]

Thanks for the bug report.

Next time the screen stays purple, please:

1. Wait 10 seconds.

2. Reboot and login with password.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. 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.

6. If step 5 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.

[Johannes Zeiser (johannes-zeiser5)]

Here is the file from step 3

The directory /var/crash is empty, or at least ls /var/crash/ does not return anything.

There are some error reports, but just about onedrive and they are from last year, so I doubt they are relevant for this problem.

[Daniel van Vugt (vanvugt)]

I can't see the cause of the problem in that log, sorry.

[Daniel van Vugt (vanvugt)]

Given we don't see "GNOME Shell started" in that log file it seems gnome-shell probably isn't to blame here, so unassigning.

[Daniel van Vugt (vanvugt)]

Maybe another fprintd issue. See also bug 1960336.