Bug 514347

Summary: Unable to register fingerprint
Product: [Applications] systemsettings Reporter: Eskil Mork <eskil>
Component: kcm_usersAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: minor CC: kde, nate, uhhadd
Priority: NOR    
Version First Reported In: 6.5.4   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The part where it stops registering my fingerprint, sometimes it gets further, but it never fully registers

Description Eskil Mork 2026-01-08 20:58:26 UTC
Created attachment 188333 [details]
The part where it stops registering my fingerprint, sometimes it gets further, but it never fully registers

I'm unable to register fingerprints on my Acer Swift SFX14-72G.
After clicking the button to configure fingerprint authentication, entering my password and selecting a finger to register, the system clearly picks up on my fingerprint reader as i can press it until it is registered about 40 to 50% and then it just stops registering anything, and my fingerprint isn't saved.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.18.3-200.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 22 × Intel® Core™ Ultra 7 155H
Memory: 16 GiB of RAM (15.0 GiB usable)
Graphics Processor 1: Intel® Arc
Graphics Processor 2: NVIDIA GeForce RTX 3050 6GB Laptop GPU
ADDITIONAL INFORMATION
I got the same result in Nobara linux, however the fingerprint sensor works as expected in Debian with Gnome
Comment 1 Nate Graham 2026-01-08 22:22:22 UTC
Does the same thing happen if you use the `fprintd-enroll` to register a fingerprint?
Comment 2 Eskil Mork 2026-01-09 01:37:19 UTC
(In reply to Nate Graham from comment #1)
> Does the same thing happen if you use the `fprintd-enroll` to register a
> fingerprint?

yes it appears so, the output of the command is:
"Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-finger-not-centered
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-stage-passed
Enroll result: enroll-finger-not-centered
Enroll result: enroll-remove-and-retry
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-remove-and-retry
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-remove-and-retry
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-duplicate"
Comment 3 Eskil Mork 2026-01-09 01:42:08 UTC
(In reply to Eskil Mork from comment #2)
> (In reply to Nate Graham from comment #1)
> > Does the same thing happen if you use the `fprintd-enroll` to register a
> > fingerprint?
> 
> yes it appears so, the output of the command is:
> "Using device /net/reactivated/Fprint/Device/0
> Enrolling right-index-finger finger.
> Enroll result: enroll-stage-passed
> Enroll result: enroll-finger-not-centered
> Enroll result: enroll-stage-passed
> Enroll result: enroll-remove-and-retry
> Enroll result: enroll-stage-passed
> Enroll result: enroll-finger-not-centered
> Enroll result: enroll-remove-and-retry
> Enroll result: enroll-stage-passed
> Enroll result: enroll-remove-and-retry
> Enroll result: enroll-remove-and-retry
> Enroll result: enroll-stage-passed
> Enroll result: enroll-stage-passed
> Enroll result: enroll-remove-and-retry
> Enroll result: enroll-stage-passed
> Enroll result: enroll-stage-passed
> Enroll result: enroll-duplicate"

Further more "fprintd-list eskil" returns 
"found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User eskil has no fingers enrolled for FPC L:0000 FW:1425037."
Comment 4 Nate Graham 2026-01-09 01:53:57 UTC
Thanks. That means the issue is below the System Settings UI, meaning it's not a KDE bug. The issue may be in any of the following:
- Your local configuration
- The Fprint library
- The drivers for your specific fingerprint reader

If you're having trouble figuring out which, I'd recommend reading out to your distro's developers, as the distro is ultimately responsible for final system integration.