Created attachment 178195 [details] Updates list SUMMARY STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake laptop from sleep 3. Attempt to login with fingerprint OBSERVED RESULT No option for fingerprint login EXPECTED RESULT Option for fingerprint login should be shown SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I've been using fingerprint authentication for sudo and screen unlocking for a few months. I am not using it for initial login. I've had no issues with fingerprint authentication in all this time, until the 9/10th of February. Fingerprint authentication still works for sudo authentication and for unlocking the screen after I've manually locked it via Meta + L. However the system is no longer prompting me for fingerprint authentication after it wakes from sleep e.g. I close my laptop lid, wait a minute and then reopen the laptop, I'm no longer prompted with the "or scan your fingerprint on the reader" message and I have to use password auth. The same issue applies if I use the "sleep" option in the application menu. I see the following fprintd related messages in the journal log after waking from sleep and seeing the missing "place your finger..." message on the lock screen. ``` Feb 12 15:47:28 fedora-xps systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Feb 12 15:47:29 fedora-xps systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Feb 12 15:47:29 fedora-xps fprintd[11244]: Authorization denied to :1.248 to call method 'Claim' for device 'Goodix MOC Fingerprint Sensor': Device was already claimed Feb 12 15:48:16 fedora-xps fprintd[11244]: Authorization denied to :1.258 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor': Not Authorized: net.reactivated.fprint.device.verify Feb 12 15:49:19 fedora-xps systemd[1]: fprintd.service: Deactivated successfully. ``` I've rolled back to a BTRFS snapshot from February 5th and the fingerprint functionality works fine when waking from sleep. However if I apply updates, the problem returns. So it seems like some update between 05/02/2025 and maybe the 9th/10th started the issue. I've attached a list of the updates that are applied before the issue returns.
I've done some more testing. I rolled back to the functioning btrfs snapshot and applied all updates except for kde-polkit and kscreenlocker. However this didn't prevent the issue. Still seeing the same error messages related to fprintd in journal logs: ``` Feb 13 14:06:40 fedora-xps systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Feb 13 14:06:41 fedora-xps systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Feb 13 14:06:49 fedora-xps fprintd[6203]: Authorization denied to :1.129 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor': Not Authorized: net.reactivated.fprint.device.verify Feb 13 14:07:31 fedora-xps systemd[1]: fprintd.service: Deactivated successfully. Feb 13 14:11:11 fedora-xps systemd[1]: Starting fprintd.service - Fingerprint Authentication Daemon... Feb 13 14:11:11 fedora-xps systemd[1]: Started fprintd.service - Fingerprint Authentication Daemon. Feb 13 14:11:13 fedora-xps fprintd[8200]: Verification was in progress, stopping it Feb 13 14:11:36 fedora-xps fprintd[8200]: Authorization denied to :1.190 to call method 'ListEnrolledFingers' for device 'Goodix MOC Fingerprint Sensor': Not Authorized: net.reactivated.fprint.device.verify Feb 13 14:12:09 fedora-xps systemd[1]: fprintd.service: Deactivated successfully. ``` Fingerprint functionality works as expected for everything except for the unlock screen when waking from sleep. I can still use fingerprint auth for sudo and unlock screen after manually locking the screen with Meta + L key combo or menu shortcut.
I've attached a konsole output of the updates that were applied to replicate the issue.
Created attachment 178270 [details] konsole output of applied updates
Created attachment 178274 [details] fprintd journal logs after polkit changes I've done some digging and it seems like the fprintd errors are polkit related. Based on this comment (https://github.com/i3/i3lock/issues/210#issuecomment-1033042602) I created two rules in this directory '/etc/polkit-1/rules.d/': 50-net.reactivated.fprint.device.claim.rules and 50-net.reactivated.fprint.device.verify.rules After creating these rules, I'm no longer getting the fprintd authorisation denied messages in my journal logs. However the fingerprint authentication is still failing to appear on the unlock screen after the machine goes to sleep. I think that I've also made another breakthrough. I noticed that if I wake the machine from sleep very quickly, the fingerprint authentication option is still there. Under System Settings > Screen Locking I have the "Delay before password required" option set to 30 seconds. If I wake the laptop from sleep before 30 seconds, the fingerprint option is there, but if I wake the laptop after longer than 30 seconds the fingerprint option is no longer there. I can replicate this behaviour with other time delays for the "Delay before password required" setting. However setting this to "Never require a password" simply means that the machine never locks and isn't suitable for anyone with any security considerations. So could this be an issue with my settings under pam.d? I'm a bit lost with these settings and especially lost when it comes to how they interact with kscreenlocker
Created a bug report for this on the Fedora bugzilla too: https://bugzilla.redhat.com/show_bug.cgi?id=2345554 Uncertain if there or here is the best place to report. Apologies, I'm new to this bug reporting business.
It seems that this isn't just present on Fedora. An arch user mentioned the same bug in this reddit thread: https://www.reddit.com/r/kde/comments/1ikzm9q/fingerprint_unlock_not_working_after_screen/ There's also another Fedora user reporting the same issue.
(In reply to chwshka from comment #4) > I think that I've also made another breakthrough. I noticed that if I wake > the machine from sleep very quickly, the fingerprint authentication option > is still there. Under System Settings > Screen Locking I have the "Delay > before password required" option set to 30 seconds. If I wake the laptop > from sleep before 30 seconds, the fingerprint option is there, but if I wake > the laptop after longer than 30 seconds the fingerprint option is no longer > there. > > I can replicate this behaviour with other time delays for the "Delay before > password required" setting. However setting this to "Never require a > password" simply means that the machine never locks and isn't suitable for > anyone with any security considerations. > > So could this be an issue with my settings under pam.d? I'm a bit lost with > these settings and especially lost when it comes to how they interact with > kscreenlocker Following on from this. I've set the "Delay before password required" setting to "Never require a password". When I wake the computer from sleep I noticed that the "or scan your fingerprint on the reader" message is still there on the lock screen and is functional. If I put my finger to the reader, it unlocks. If I use an incorrect finger, it gives the usual error. Although because the "Never require a password" setting is in effect, I can also just hit any key or move the mouse to unlock. So beyond the fprintd polkit errors that I previously mentioned, this regression seems related to the "Delay before password required" option.
I'm having the same problem. It will ask for my fingerprint if i lock the screen using Super+L, But not if the laptop is put to sleep. I haven't made any changes to PAM or anything, its a fresh install. Plasma 6.1.3 Arch linux Thinkpad P53
Hi, I can reproduce the same behavior on two computers: 1) Arch Linux - Plasma 6.3.0 on Wayland - KDE Frameworks 6.11.0 - Thinkpad T14s Gen 6 AMD 2) KDE Neon (Ubuntu) - Plasma 6.2.5 on Wayland - KDE Frameworks 6.10.0 - Thinkpad P14s Gen 2 AMD The fingerprint is not available after wake from sleep. It only works if I press enter in the (empty) password field and wait few seconds until the password input reappears. On the newer Thinkpad T14s Gen 6 the fingerprint reader (integrated to power button) activity is displayed by changing color of the LED from white to green. But when waking from sleep, the LED color does not even change to green, so it seems like the reader it is not even activated on hardware level.
*** Bug 500357 has been marked as a duplicate of this bug. ***
I have the same problem, but I get these fprintd logs: ``` Feb 18 20:13:57 archlinux systemd[1]: Starting Fingerprint Authentication Daemon... Feb 18 20:13:58 archlinux fprintd[21638]: Failed to install a sleep delay inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgre> Feb 18 20:13:58 archlinux systemd[1]: Started Fingerprint Authentication Daemon. Feb 18 20:14:03 archlinux fprintd[21638]: Device reported an error during verify: device was disconnected ```
I've seen this intermittently, and just this morning on 6.3.0 I have similar journalctl logs as the original report with "Authorization denied" as the system is put to sleep
I am seeing the same thing. It would appear that when the system sleeps or the screen locks due to timeout or meta-L, authentication is immediately (if invisibly) requested. If I attempt to unlock/wake the system immediately, I can use my fingerprint. If I wait (30 seconds, perhaps?) then the authentication fails and then attempting to wake/unlock the system will no longer request or honor a fingerprint. Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.15-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 27.2 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7
Can confirm the same thing. Operating System: EndeavourOS KDE Plasma Version: 6.3.1 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.12.16-1-lts (64-bit) Graphics Platform: Wayland Processors: 12 × 13th Gen Intel® Core™ i5-1345U Memory: 31.0 GiB of RAM Graphics Processor: Intel® Iris® Xe Graphics Manufacturer: LENOVO Product Name: 21FKS4LN00 System Version: ThinkPad L13 Yoga Gen 4
Just updated last night with the latest packages from pacman and the issue with the fingerprint reader is still there. Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 31.0 GiB of RAM Graphics Processor 1: Mesa Intel® UHD Graphics 630 Graphics Processor 2: llvmpipe Manufacturer: LENOVO System Version: ThinkPad P53
I can replicate this issue too. The fingerprint sensor always works fine for locking the screen, and I can unlock it with my fingerprint. However, after suspending, the fingerprint option is no longer available, and holding my finger on the scanner does nothing. Pressing Enter while holding my finger on the scanner also has no effect. Kinfo: Operating System: Arch Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.5-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i5-1145G7 @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Intel® Iris® Xe Graphics Only Error in Journalctl is the following: [9176]: Failed to install a sleep delay inhibitor: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running
Running KDE 6.3.3 and it seems to be working, but there are still moments where it has issues. If I run into an issue, such as leaving the laptop to sleep on its own, it will result with the following. ``` Mar 13 00:01:53 soulis-ThinkPad systemd[1]: Starting Fingerprint Authentication Daemon... Mar 13 00:01:53 soulis-ThinkPad fprintd[24304]: Device responded with error: 789 retry: 1 Mar 13 00:01:53 soulis-ThinkPad systemd[1]: Started Fingerprint Authentication Daemon. ``` What I've noticed is if the sleep is issued, it begins 'starting' the authentication daemon, and is 'started' upon wake with all the successful unlocks. I'll update if anything else is observed.
Probably duplicate of bug#492315
I'm seeing the same problem: fingerprint unlock works after locking (with, e.g., Meta+L), but not after sleeping (I do get the "or scan your fingerprint on the reader" in both cases, though).
I'm using latest manjaro, plasma/kde version 6.3.3-1. After suspend and/or screen lock + ~1 min of idle, I cannot use fingreprint anymore. However, when I hibernated the system, I could use fingerprint after wake up.
(In reply to kde from comment #19) > I'm seeing the same problem: fingerprint unlock works after locking (with, > e.g., Meta+L), but not after sleeping (I do get the "or scan your > fingerprint on the reader" in both cases, though). This sounds like a different issue. In this bug, the prompt to scan your fingerprint doesn't appear at all.
(In reply to TraceyC from comment #21) ... > This sounds like a different issue. In this bug, the prompt to scan your > fingerprint doesn't appear at all. Here's what I see: * When I lock with Meta-L and then immediately unlock, I get the password prompt, with the "or scan your fingerprint on the reader" below it, and fingerprint unlocking works. * When I sleep and then immediately wake, I get exactly the same thing, but fingerprint unlock doesn't work. (There's also an additional bug: although the unlock screen appears fairly quickly, and the cursor appears and can be moved around the screen, typed keys do not immediately appear in the password box, and the system doesn't immediately unlock upon typing the password. After some more time has elapsed, the typed keys all appear together / the system unlocks if the password + enter have been previously typed.) * Sometimes (when the system has been sleeping for a while?), in addition to the "or scan your fingerprint on the reader" *below* the password box, I also get the messages "Place your finger on the fingerprint reader" and "Verification has timed out" *above* the box, and in this case as well fingerprint unlock does not work. I have no idea how many separate bugs this is: KDE / SDDM unlocking is so full of bugs that I'm on the verge of abandoning KDE entirely after trying it for a few months, even though there's a lot I do like about it. In addition to the problem(s) discussed above, I've encountered: * https://bugs.kde.org/show_bug.cgi?id=497904 * https://bugs.kde.org/show_bug.cgi?id=498101 * https://bugs.kde.org/show_bug.cgi?id=498099
(In reply to kde from comment #22) > (In reply to TraceyC from comment #21) > ... > > > This sounds like a different issue. In this bug, the prompt to scan your > > fingerprint doesn't appear at all. > > Here's what I see: > > * When I lock with Meta-L and then immediately unlock, I get the password > prompt, with the "or scan your fingerprint on the reader" below it, and > fingerprint unlocking works. > > * When I sleep and then immediately wake, I get exactly the same thing, but > fingerprint unlock doesn't work. (There's also an additional bug: although > the unlock screen appears fairly quickly, and the cursor appears and can be > moved around the screen, typed keys do not immediately appear in the > password box, and the system doesn't immediately unlock upon typing the > password. After some more time has elapsed, the typed keys all appear > together / the system unlocks if the password + enter have been previously > typed.) > > * Sometimes (when the system has been sleeping for a while?), in addition to > the "or scan your fingerprint on the reader" *below* the password box, I > also get the messages "Place your finger on the fingerprint reader" and > "Verification has timed out" *above* the box, and in this case as well > fingerprint unlock does not work. > > I have no idea how many separate bugs this is: KDE / SDDM unlocking is so > full of bugs that I'm on the verge of abandoning KDE entirely after trying > it for a few months, even though there's a lot I do like about it. In > addition to the problem(s) discussed above, I've encountered: > > * https://bugs.kde.org/show_bug.cgi?id=497904 > * https://bugs.kde.org/show_bug.cgi?id=498101 > * https://bugs.kde.org/show_bug.cgi?id=498099 This does sound like a slightly different bug, although it's likely related. My issue: 1) Meta + L works fine. 2) Sleep, immediate wake and then fingerprint unlock works fine. Specifically it works until the amount of time defined under "Screen Locking" > "Delay before password required" has passed. 3) After that "Delay before password required" amount of time has passed, the fingerprint unlock option isn't shown and doesn't work. I'd be curious if you're getting similar polkit errors as I mentioned in my first few comments.
(In reply to Kyle from comment #8) > I'm having the same problem. It will ask for my fingerprint if i lock the > screen using Super+L, But not if the laptop is put to sleep. > > I haven't made any changes to PAM or anything, its a fresh install. > > Plasma 6.1.3 > Arch linux > Thinkpad P53
STEPS TO REPRODUCE 1. Put laptop to sleep 2. Wake laptop from sleep 3. Attempt to login with fingerprint OBSERVED RESULT No option for fingerprint login EXPECTED RESULT Option for fingerprint login should be shown SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.3 KDE Frameworks Version: 6.12.0 Qt Version: 6.8.2 Kernel Version: 6.13.8-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland HARDWARE 16 x 12th Gen Intel Core i5-1240P Framework Laptop ADDITIONAL INFORMATION Up until recently I was able to unlock the laptop with my fingerprint censor, but now (as stated by others here) I'm only able to do so when explicitly locking with the key combo I set up to do so. It didn't matter if I locked it like this, or closed the lid, when I'd open it up I could use my finger to unlock it. Additionally, I did notice in the settings, under Users, that there's a message that states: "Fingerprints can be used in place of a password when unlocking the screen and providing administrator permissions to applications and command-line programs that request them. Logging into the system with your fingerprint is not yet supported." I can understand when first booting up the machine that you may need to input a password, but every time the screen locks due to the computer going idle, or locking it manually, using the fingerprint censor should work, if I'm reading things correctly.
Setting to confirmed since multiple people can reproduce this