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 bugzilla.redhat.com.
Bug 1933282 - System doesn't show the "(or swipe finger)" text for indicate user login by fingerprint after Restart with 5mins idle
Summary: System doesn't show the "(or swipe finger)" text for indicate user login by f...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 34
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-26 13:59 UTC by Julius Endrina
Modified: 2021-05-27 13:45 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)
Journalctl log when the problem was encountered. (955.16 KB, text/plain)
2021-02-26 13:59 UTC, Julius Endrina 		no flags Details
View All

Description Julius Endrina 2021-02-26 13:59:46 UTC 
Created attachment 1759503 [details]
Journalctl log when the problem was encountered.

Description of problem: In Panther systems (ThinkPad X1 Yoga Gen6) with Fedora 33 OS, System doesn't show the "(or swipe finger)" text for indicate user login by fingerprint after Restart then idle for 5mins before select user account to login.


Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Prepare Panther SIT machine and Install fedora 33 image.
2. Boot to OS.
3. Go to Settings -> Users -> Click Fingerprint Login section, follow the instructions to enroll Fingerprint.
4. Once finger is enrolled successfully, Perform restart.
5. Leave system idle for 5 mins. --> Keypoint
6. Select user account to login.
7. Observe that the Under the input password section, "(or swipe finger)" text is not shown to indicate that there is an option to login by fingerprint.==>Problem


Actual results:
Under the input password section, "(or swipe finger)" text is not shown to indicate that there is an option to login by fingerprint.

Expected results:
After resume from PM, under the input password section, "(or swipe finger)" text is shown to indicate that there is an option to login by fingerprint.

Additional info:
ROM: N32ET32W
ECFW: N32HT31W
ME: N32RN16W
OS Version: Fedora 33
Kernel: 5.10.10-200.fc33.x86_64
FPR Vendor: Synaptics
Promotheus: 10.01.3273255
IOTA Config: 0004
Comment 1 Ganapathi Kamath 2021-02-28 22:11:12 UTC 
Mentioned in Bug 1933520
Comment 2 Mark Pearson 2021-04-14 15:35:25 UTC 
Hi Benjamin,

I looked through the linked bug and I don't think it's related to this issue. 

I think we had similar to this before and my understanding is the very first logon after a reboot needs a password to basically unlock the keychain, but subsequent logon's (from suspend/lock) can use fingerprint - so this issue is really 'working as designed'.

Let me know if you think otherwise and if this is a valid bug. As an aside I'm personally not seeing the 'leave system idle for 5 mins' keypoint above - I don't get fprint on first login regardless.

Mark
Comment 3 Benjamin Berg 2021-05-27 13:45:17 UTC 
So, this is a valid bug, because there is a race condition in gnome-shell when fprintd is slow to start up (compared to PAM verification start).

That said, fixing that bug will make the problem with unlocking the keyring more visible. So, there is a second problem there where we should prevent fingerprint login (unfortunately, I am not completely sure how we can properly achieve that).

Moving to gnome-shell for the first issue. The _checkForFingerprintReader async handler should run "this._startService(FINGERPRINT_SERVICE_NAME);" when normal password verification is already running.
Note You need to log in before you can comment on or make changes to this bug.