Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When using fingerprint reader to login, gdm won't show any information about the swipe result, no msg to swipe again, when there was a fail to match fingerprint.
Looking at the log, the pam messages are received but they are not passed to user.
[snip]
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 4 with payload 'Swipe your finger across the fingerprint reader'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 3 with payload 'Failed to match fingerprint'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 4 with payload 'Swipe your finger across the fingerprint reader'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 3 with payload 'Failed to match fingerprint'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 4 with payload 'Swipe your finger across the fingerprint reader'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: 1 new messages received from PAM
gdm-fingerprint][6727]: GdmSessionWorker: username is 'test'
gdm-fingerprint][6727]: GdmSessionWorker: old-username='test' new-username='test'
gdm-fingerprint][6727]: GdmSessionWorker: received pam message of type 3 with payload 'Failed to match fingerprint'
gdm-fingerprint][6727]: GdmSessionWorker: PAM conversation returning 0: Success
gdm-fingerprint][6727]: GdmSessionWorker: authentication returned 7: Authentication failure
gdm-fingerprint][6727]: GdmSessionWorker: uninitializing PAM
gdm-fingerprint][6727]: GdmSessionWorker: jumping to VT 1
Version-Release number of selected component (if applicable):
gdm-3.28.2-7.el7.x86_64
fprintd-0.8.1-1.el7
libfprint-0.8.2-1.el7
gnome-shell-3.28.3-1.el7
Comment 3Ray Strode [halfline]
2018-08-29 13:31:31 UTC
unless you have password authentication disabled, this is by design:
} else if (serviceName == FINGERPRINT_SERVICE_NAME &&
this._haveFingerprintReader) {
// We don't show fingerprint messages directly since it's
// not the main auth service…
Comment 7RHEL Program Management
2021-02-15 07:42:04 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.