Bug 509542 - Erroneous lock screen invitations to use fingerprint scanner when that is not enabled/configured
Summary: Erroneous lock screen invitations to use fingerprint scanner when that is not...
Status: RESOLVED DUPLICATE of bug 505987
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.4.80
Platform: KDE Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-16 01:04 UTC by William Ethridge
Modified: 2025-09-16 16:54 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description William Ethridge 2025-09-16 01:04:50 UTC 
SUMMARY
My laptop has a fingerprint scanner, but it is likely not detected in Linux.

Initial sign-in does not offer fingerprint sign-in, but coming back from lock screen does?

I do not see any settings or options to configure fingerprint scanning for lock screen or authentication.

STEPS TO REPRODUCE
1. on boot, login screen show no indications of fingerprint scanning functionality
2. in Settings, there is no listed option to configure fingerprint scanning.
3. on screen lock, it offers to use a fingerprint scanner.

OBSERVED RESULT
fingerprint scanner is not detected

EXPECTED RESULT
if there is no fingerprint scanner detected, it shouldn't offer fingerprint signin.
Ideally I would like to try out the fingerprint scanner on this device though.

SOFTWARE/OS VERSIONS
Operating System: KDE Linux 2025-09-15
KDE Plasma Version: 6.4.80
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.7-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® N150
Memory: 12 GiB of RAM (11.4 GiB usable)
Graphics Processor: Intel® Graphics


ADDITIONAL INFORMATION
Comment 1 TraceyC 2025-09-16 16:54:57 UTC 
Thanks for the bug report. This had been reported in bug 505987, so I'm merging this report into the existing one. Please follow that report for updates.

*** This bug has been marked as a duplicate of bug 505987 ***