Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1935331 - unable to login on laptop with fingerprint reader
Summary: unable to login on laptop with fingerprint reader
Alias: None
Product: Fedora
Classification: Fedora
Component: authselect
Version: 34
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Pavel Březina
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F34BetaBlocker 1937308
TreeView+ depends on / blocked
Reported: 2021-03-04 16:27 UTC by louisgtwo
Modified: 2021-03-12 01:35 UTC (History)
14 users (show)

Fixed In Version: authselect-1.2.2-6.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1937308 (view as bug list)
Last Closed: 2021-03-12 01:35:54 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github authselect authselect pull 239 0 None open fingerprint: Retain error code returned by 2021-03-09 13:39:42 UTC

Description louisgtwo 2021-03-04 16:27:30 UTC
With a Dell inspiron 7370 loaded with f34 as of 3/3/21 I am unable to login with password. gdm seems to be in a loop looking for a fingerprint login which is not setup yet as this is a fresh install.

Loading f34 in a virt machine gdm login works fine.

Comment 1 Ganapathi Kamath 2021-03-08 01:24:21 UTC
Same as Bug 1933520 , which was closed abruptly/prematurely without explanation. This bug exists

Comment 2 Alessio 2021-03-08 12:35:44 UTC
I can confirm that 
Toshiba Portege R930-163

Also in a live session. If you set the liveuser password and you lock the screen there is no way to log in.

Comment 3 Alessio 2021-03-08 12:43:06 UTC
In the logs there is this line at each iteration

Mar 08 12:41:48 localhost-live audit[2707]: USER_AUTH pid=2707 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=? acct="liveuser" exe="/usr/libexec/gdm-session-worker" hostname=localhost-live addr=? terminal=/dev/tty1 res=failed'

Comment 4 louisgtwo 2021-03-09 01:18:02 UTC
Looking Bug 1933520 it seems to be an issue with authselect not disabling fprint when it is not setup. I will wait until authselect-1.2.2-5 hits f34 to test again.

Comment 5 Benjamin Berg 2021-03-09 13:39:44 UTC
It turns out that the fingerprint-auth stack would also return a failure when the stack was enabled. I posted

upstream to fix this. We'll need to pull this into F34.

Comment 6 Fedora Blocker Bugs Application 2021-03-09 13:41:02 UTC
Proposed as a Blocker and Freeze Exception for 34-beta by Fedora user benzea using the blocker tracking app because:

 This breaks login/unlock in GDM/GNOME if the machine has a fingerprint reader and the user has no enrolled prints.

Comment 7 Adam Williamson 2021-03-09 18:28:41 UTC
+4 in , marking accepted.

Comment 8 Adam Williamson 2021-03-09 18:30:10 UTC
Um. Well, actually I'm not sure about that. Is it that breaks this? If so, it can't be a blocker, as that is not stable (and so not included in composes), it's in -testing only. Unaccepting for now.

Comment 9 Adam Williamson 2021-03-09 18:35:06 UTC
(adamw) benzea: do we know when broke?
(benzea) adamw: yeah, GDM update to 40.x
(benzea) er, I mean gnome-shell

So sounds like this is broken in current F34 stable, so accepting again.

Comment 10 louisgtwo 2021-03-09 18:54:18 UTC
No, fixes the login problem.

Comment 11 Benjamin Berg 2021-03-09 18:58:51 UTC
Before there is more confusion, there are two separate bugs, that result in exactly the same issue for users.

 1. If fingerprint-auth is disabled, the fingerprint-auth stack always fails with AUTH_ERR, resulting in the retry from GDM. In this case authselect needs to disable the GDM fingerprint auth, but this was not done in the "minimal" profile, causing issues. This is what fixes.
 2. If fingerprint-auth is enabled, the fingerprint-auth stack will always fail rather than returning the PAM_AUTHINFO_UNAVAIL from, confusing GDM/gnome-shell. This is what the next update will fix.

Note that there was some confusion, and the previous bug 1933520 was probably about issue 2 while in fact we addressed issue 1 there.

Comment 12 Fedora Update System 2021-03-09 19:56:48 UTC
FEDORA-2021-d2afa6dc55 has been submitted as an update to Fedora 34.

Comment 13 Fedora Update System 2021-03-09 19:56:52 UTC
FEDORA-2021-d2afa6dc55 has been submitted as an update to Fedora 34.

Comment 14 Adam Williamson 2021-03-09 19:59:02 UTC
I've now edited the update to include a build with *both* fixes. Please verify if that works, thanks!

Comment 15 louisgtwo 2021-03-09 21:05:49 UTC
With authselect-1.2.2-6 after entering password gdm just spins. Can not login.

Comment 16 Benjamin Berg 2021-03-09 21:26:04 UTC
Yes, but that is a different issue (which is likely in gnome-shell). Login will work if you simply try again. It seems to only occur right after booting, we are not yet clear why though.

So, again, "gdm just spinning" is *not* this bug and actually a *good* sign that the authselect part is fixed!

Comment 17 Fedora Update System 2021-03-09 22:45:40 UTC
FEDORA-2021-d2afa6dc55 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d2afa6dc55`
You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 18 Ben Cotton 2021-03-11 17:47:49 UTC
Fix is verified in RC1

Comment 19 Fedora Update System 2021-03-12 01:35:54 UTC
FEDORA-2021-d2afa6dc55 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.