Bug 622561
Summary: | authentication method buttons show and disappear before they can be used | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | jmccann |
Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | cschalle, otaylor, rstrode, tpelka |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | gdm-2.30.4-29.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-12-06 18:08:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
jmccann
2010-08-09 18:45:44 UTC
So what's going on here is, - you don't have smartcards enabled - you don't have a fingerprint reader The authentication buttons show up briefly because you do have fingerprint authentication enabled, but then fails shortly there after since you don't have a reader. The gdm code won't show the authentication method buttons if you only have one authentication method available. We could probably avoid showing the buttons at all if you don't have a fingerprint reader. That would likely require changes to fprintd and the gdm fingerprint plugin. It's not blocker material at this point, though. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. 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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1721.html |