attempting to enable fingerprint with pam-auth-update breaks gdm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pam (Debian) |
Fix Released
|
Unknown
|
|||
pam (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I ran sudo pam-auth-update, enabled "Fingerprint authentication", selected "OK", and then rebooted.
GDM wouldn't start after the reboot:
Feb 27 06:29:41 jik-x1 /usr/lib/
Feb 27 06:29:41 jik-x1 /usr/lib/
Feb 27 06:29:41 jik-x1 /usr/lib/
I logged in on a VT and ran pam-auth-update again. I observed that "Register user sessions in the systemd control group" was not selected, even though my recollection was that it had been selected before I enabled fingerprint authentication, and I didn't disable it.
I unselected fingerprint authentication and selected "Register user sessions in the systemd control group" and rebooted again. GDM started working again.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: libpam-runtime 1.3.1-5ubuntu1
ProcVersionSign
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 27 06:31:32 2019
InstallationDate: Installed on 2019-02-26 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitec
SourcePackage: pam
UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago)
Changed in pam (Debian): | |
status: | Unknown → Incomplete |
Changed in pam (Debian): | |
status: | Incomplete → Fix Released |
Actually, it's even weirder than that.
I went through all this several times while trying to narrow down the repro steps, and it's all very bizarre. Somehow I managed to get gdm working again, and then in a logged in gdm session, I enabled fingerprint, and exited from pam-auth-update, then ran pam-auth-update again and disabled fingerprint and re-enabled register user sessions which had once again somehow magically gotten disabled, but then I ran pam-auth-update a third time and register user sessions was STILL disabled even though I'd just enabled it, and then when I rebooted GDM wouldn't work again. So at that point I logged in on a VT and ran pam-auth-update again and selected register user sessions again, and then just out of curiosity ran pam-auth-update again and this time register user sessions was still selected, so I exited and rebooted and GDM worked again.
There is something very bizarre going on here.