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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1817897 Title: attempting to enable fingerprint with pam-auth-update breaks gdm Status in pam package in Ubuntu: New 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/gdm3/gdm-wayland-session[1551]: dbus-daemon[1553]: [session uid=121 pid=1553] Activating service name='org.freedesktop.systemd1' requested by ':1.0' (uid=121 pid=1551 comm="/usr/lib/gdm3/gdm-wayland-session gnome-session --" label="unconfined") Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: dbus-daemon[1553]: [session uid=121 pid=1553] Activated service 'org.freedesktop.systemd1' failed: Process org.freedesktop.systemd1 exited with status 1 Feb 27 06:29:41 jik-x1 /usr/lib/gdm3/gdm-wayland-session[1551]: Unable to register display with display manager 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 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 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) PackageArchitecture: all SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-02-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1817897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
