Bug 500451 - Locker turns a fingerprint scanner on before system suspend
Summary: Locker turns a fingerprint scanner on before system suspend
Status: RESOLVED DUPLICATE of bug 481808
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (show other bugs)
Version: 6.3.0
Platform: Neon Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-20 10:16 UTC by Grief
Modified: 2025-02-21 01:36 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grief 2025-02-20 10:16:09 UTC
STEPS TO REPRODUCE
1. I am using this device: https://www.key-id.com/fido2-key-with-windows-hello/
2. I have installed pam-u2f: https://github.com/Yubico/pam-u2f.git
3. I configured locking in /etc/pam.d/fingerprint as:
    > auth sufficient pam_u2f.so authfile=/etc/u2f_keys userverification=1 cue

OBSERVED RESULT
When I close the lid of my MSI Raider GE77HX 12UGS to suspend the system, the LED on the fingerprint reader turns on and stays on until I open the lid again to resume the system.

If I remove the device and plug it back in while the system is suspended, the LED does not turn on. However, after opening the lid, the lock screen becomes unresponsive, and I need to unlock the system from TTY.

EXPECTED RESULT
Before KDE 6.3, the LED was only enabled after opening the lid, and everything worked flawlessly. This looks like a regression.

SOFTWARE/OS VERSIONS
Operating System: Ubuntu 24.10 (Oracular Oriole)
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.11.0-1010-lowlatency (64-bit)
Graphics Platform: Wayland
Processors: 24 × 12th Gen Intel® Core™ i7-12800HX
Memory: 31.1 ГиБ of RAM
Graphics Processor: NVIDIA GeForce RTX 3070 Ti Laptop GPU

ADDITIONAL INFORMATION
Probably regression
Comment 1 fanzhuyifan 2025-02-21 01:36:44 UTC

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