FS#70575 - gdm login stuck in fingerprint authentication loop
Attached to Project:
Arch Linux
Opened by Julian Phillips (chr0mag) - Saturday, 24 April 2021, 20:35 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 21:41 GMT
Opened by Julian Phillips (chr0mag) - Saturday, 24 April 2021, 20:35 GMT
Last edited by Toolybird (Toolybird) - Friday, 02 June 2023, 21:41 GMT
|
Details
After upgrading to gdm 40.0-1 the login screen gets stuck in
a loop with the following message appearing every few
seconds: "Sorry, fingerprint authentication did not work.
Please try again." This happens without any user input.
Switching repeatedly (Ctrl-Alt-FX) between consoles somehow
got me to a usable login prompt.
-Enabling fingerprint login appears to avoid the problem. -A similar bug can be found here: https://bugzilla.redhat.com/show_bug.cgi?id=1933520 . -For now, I've edited /etc/pam.d/gdm-fingerprint as described in comment 41 of that ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1933520#c41 Replace: auth [success=1 default=ignore] pam_fprintd.so With: auth [success=done default=bad] pam_fprintd.so This looks like the upstream bug: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3853 -- but logging this as its not clear to me whether the change to /etc/pam.d/gdm-fingerprint is also required. |
This task depends upon
Closed by Toolybird (Toolybird)
Friday, 02 June 2023, 21:41 GMT
Reason for closing: Fixed
Additional comments about closing: Old and stale. Assuming no longer an issue i.e. it's been fixed somehow in subsequent updates.
Friday, 02 June 2023, 21:41 GMT
Reason for closing: Fixed
Additional comments about closing: Old and stale. Assuming no longer an issue i.e. it's been fixed somehow in subsequent updates.
Had to run "systemctl stop fprintd.service" and "faillock --user mushotoku --reset" multiple times, till i can login.
I worked around by uninstalling "libfprint" and "fprintd" for now.