RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
The fingerprint login is not available after one uses an unenrolled/wrong finger.

Version-Release number of selected component (if applicable):
fprintd-1.90.8-1.el8.x86_64
libfprint-1.90.6-1.el8.x86_64
gdm-3.28.3-35.el8.x86_64
gnome-shell-3.32.2-21.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1.Enroll a new fingerprint in Settings
2.Logout
3.Use an unenrolled/wrong finger to log in

Actual results:
The fingerprint login becomes unavailable.

Expected results:
The fingerprint login should still be available so the enrolled finger could be used for login.

Additional info:
Workarounds are: 
login with password, logout, 
hitting the cancel button (does not work in 100% cases), 
multiple uses of wrong finger in a row even required a reboot (maybe restart of fprintd could help as well)

OK, I believe I tracked down the issue. The fix is luckily relatively straight forward.

Still need to add more CI tests for this and other corner cases.

For some reason I didn't spot this while reporting #1909669. That can be marked as duplicated and closed perhaps while resolution being worked via this instead.

W.

Tested with  libfprint-1.90.7-1.el8.x86_64 and fprintd-1.90.9-1.el8.x86_64 fprintd-pam-1.90.9-1.el8.x86_64. Everything work as expected.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (libfprint bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2021:1889