https://bugs.kde.org/show_bug.cgi?id=525146
Bug ID: 525146
Summary: Fingerprint unlocking becomes unavailable after
suspending from the lock screen
Classification: Plasma
Product: plasmashell
Version First 6.7.4
Reported In:
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Screen locking
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
DESCRIPTION
Fingerprint unlocking becomes unavailable when waking from sleep, when the
laptop is suspended while the lockscreen fingerprint reader is actively waiting
for input.
STEPS TO REPRODUCE
1. Lock with Meta+L.
2. Reveal the unlock prompt and confirm that fingerprint authentication is
active.
3. Click Sleep.
4. Wake the laptop and reveal the prompt again.
5. Try the fingerprint reader.
OBSERVED RESULT
Fingerprint unlocking does not work after waking. It reports "unlocking
failed", the fingerprint instruction below the password field is absent, and
scanning a fingerprint does not unlock. Password unlocking still works. Even on
subsequent locks, fingerprint unlocking may remain unavailable until fprintd is
restarted.
EXPECTED RESULT
Fingerprint and password authentication should both be available after waking.
SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 44 (KDE Plasma Desktop Edition)
KDE Plasma Version: 6.7.4
KDE Frameworks Version: 6.29.0
KScreenLocker package: kscreenlocker-6.7.4-1.fc44.x86_64
Qt Version: 6.11.2
Kernel Version: 7.1.12-200.fc44.x86_64 (64-bit)
Graphics Platform: Wayland
ADDITIONAL INFORMATION
- Laptop: Framework Laptop 13, Intel Core Ultra Series 3
- Fingerprint reader: Goodix 27c6:609c
- fprintd: 1.94.5-5.fc44
- libfprint: 1.94.100-1.fc44
While the failure was active, I restarted fprintd over SSH. This did not
restore fingerprint authentication in the existing lock screen. After unlocking
with a password and locking again, fingerprint authentication worked. Without
restarting fprintd, fingerprint authentication remained unavailable on a newly
created lock screen too.
There is an old bug report: https://bugs.kde.org/show_bug.cgi?id=462041
describing a very similar behaviour. It was marked fixed for Plasma 6, but the
same reproduction steps and symptoms occur here with Plasma 6.7.4.
journalctl reports this at the moment the laptop goes to sleep:
fprintd: Device reported an error during identify:
Cannot run while suspended.
kscreenlocker_greet: pam_fprintd(kde-fingerprint:auth):
ReleaseDevice failed: Release failed with error:
The device is still busy with another operation, please try again later.
--
You are receiving this mail because:
You are watching all bug changes.