06cb:009a verify-no-match after enroll-completed
See original GitHub issueHello everyone,
on my Thinkpad T480s running Manjaro KDE (Kernel 5.9.16), I can enroll my finger but verification then always fails. I’ve tried resetting and re-enrolling my finger multiple times.
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-completed
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: WINBIO_ANSI_381_POS_RH_INDEX_FINGER
Verify result: verify-no-match (done)
Please let me know if I need to supply more information.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Validity90/Lobby - Gitter
If I try to use fprintd-enroll on any finger, it says 'enrol completed' after only one swipe, and then won't match if i...
Read more >Fingerprint reader: Enrollment works, verification fails - Support
I can now enroll my fingerprint: $ fprintd-enroll … ... #0: WINBIO_ANSI_381_POS_RH_INDEX_FINGER Verify result: verify-no-match (done).
Read more >Enroll works but always results in verify-no-match and resets ...
The first fprintd-verify gives verify-no-match (done) and on second ... Even before deleting, after each enrollment, the output isn't the ...
Read more >Working with 06cb:009a Synaptics, Inc. · Issue #3 - GitHub
Can you check that the device vendor and the product id in /dlls/winusb/winusb.c are actually matching your hardware? By default it is. #define ......
Read more >Fingerprint works on T480 (kernel 5.8.1) : r/thinkpad - Reddit
Doesn't work for me on 5.8.1 with 06cb:009a Synaptics, ... Verify result: verify-match (done) ... SOLVED after investigating look at :.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Can confirm factory reset fixed it for me, thanks!
A factory reset forces a calibration. If you put your finger/palm on the sensor during the calibration, all subsequent attempts to enroll/verify will be very unreliable.
06cb:009a
device is special in a sense that calibration results are partly stored on both the device and the host. Whenever you calibrate the sensor, remember to delete/usr/share/python-validity/calib-data.bin
.