So, whether or not I needed to run pam-auth-update, doing so and enabling fingerprint authentication there should not cause GDM to break, nor should the other weird behavior I described above be happening.
Having said that, yes, I was trying to enable login with fingerprint. I googled how to do that on Ubuntu and found this page, https://help.ubuntu.com/stable/ubuntu-help/session-fingerprint.html.en. But when I followed the instructions there and opened the Users panel, there was nothing there about fingerprint login. So I googled more and found this page, https://askubuntu.com/questions/1049526/fingerprint- activation-on-ubuntu-18-04, which mentioned using pam-auth-update to ensure that fingerprint authentication was enabled. So I ran pam-auth- update and found that it wasn't enabled and enabled it, which led to the problems described above. If I shouldn't have had to do any of that to be able to configure fingerprint login, then something else is wrong and I don't even know where to start looking to figure out what, but regardless of that, the issues that I encountered with pam-auth-update behaving poorly are still real. -- 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