Bug 456552 - adding a fingerprint fails
Summary: adding a fingerprint fails
Status: RESOLVED UPSTREAM
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_users (other bugs)
Version First Reported In: 5.25.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-10 14:49 UTC by Matej Starc
Modified: 2025-10-20 18:06 UTC (History)
3 users (show)

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


Attachments
systemsettings terminal output (3.66 KB, text/x-log)
2022-07-10 14:49 UTC, Matej Starc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Matej Starc 2022-07-10 14:49:49 UTC
Created attachment 150514 [details]
systemsettings terminal output

SUMMARY
Adding a fingerprint fails while scanning the finger or right after a failed attempt (cannot say about a successful one because I haven't had one yet).

STEPS TO REPRODUCE
1.  Open System settings.
2.  Go to users.
3. Click on "Configure fingerprint authentication".
4.  Try adding a fingerprint.

OBSERVED RESULT
- This might be just a problem with my fingerprint scanner, but it works poorly. Even when placing my finger on the scanner, it doesn't do anything. 
- While trying to scan a fingerprint, it will stop the scanning process and display "The device was disconnected" at the top of the "Configure Fingerprints" overlay sheet window.
- After a failed attempt at scanning a fingerprint, it will automatically fail again.
- Waiting while not touching the fingerprint scanner does not trigger an error.

Here is a video to might make things a bit clearer: https://cloud.aljaxus.eu/index.php/s/5Rdf6HzGXJsFLmr


EXPECTED RESULT
- Scanning a fingerprint should not stop in the middle of the process or directly fail after a failed attempt.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.25.2
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
Kernel Version: 5.18.10-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics
Memory: 15.0 GiB of RAM
Graphics Processor: AMD RENOIR
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Zenbook UN5401QAB_UN5401QA
System Version: 1.0
Comment 1 Nate Graham 2025-10-10 16:31:52 UTC
Thank you for the bug report, and I'm sorry we weren't able to look into it yet. From the symptoms, it seems like this may be an issue with the hardware or with the Fwupd backend. Additionally, a lot has changed since it was reported; can I ask you to see if this is still an issue with Plasma 6.4 or later and hopefully later versions of Fwupd and/or the fingerprint reader's device drivers? Thanks a lot!
Comment 2 Matej Starc 2025-10-19 09:11:58 UTC
Hello,
I think I updated the firmware (tbh I don't know because if I check whether I need a reboot, it always says yes and doesn't do anything on reboot) and it still does not work (same problems happen as in the video from 3 years ago). Maybe zeenbook's aren't supported well, seeing as they still haven't implemented drivers for the fliplock in the kernel.

Basically, asus is a shitshow on linux.

 --- Current OS info ---
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.16.12-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: Zenbook UN5401QAB_UN5401QA
System Version: 1.0
Comment 3 Nate Graham 2025-10-20 18:06:36 UTC
I'm afraid all of this sounds like driver problems, yeah.