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
Mentioned in Bug 1933520
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
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.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.