You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Ubuntu 22.04] Enroll works, verify does not, no error (X1 Yoga 2nd 138a:0097) #189
Everything works according to instructions. I can install, update PAM, enroll fingers with fprintd-enroll. But the actual reading of fingerprint doesn't work. there is no error message. The fingerprint light just stays on for 10 seconds and doesn't respond to any fingerprints. Then the PAM/login/sudo request reverts to password.
This is 138a:0097 Validity Sensors, Inc. on a Lenovo ThinkPad X1 Yoga Gen 2 (20JD000WUS).
changed the title [-][Ubuntu 22.04] Enroll works, verify does not, no error[/-][+][Ubuntu 22.04] Enroll works, verify does not, no error (X1 Yoga 2nd 138a:0097)[/+]on Feb 29, 2024
I had some goofy problems on a T470 that I just setup. I could enroll just fine but then never validate, login or sudo. What appears to have fixed it is using the instructions to factory reset the firmware. This was on a machine originally setup with Windows 10 and the fingerprint reader, then reloaded with Ubuntu 22.04 (no dual boot). systemctl status python3-validity did not report errors but since I did have the sensor configured and fingerprints enrolled under Windows I took a flyer at the reset. Now login and sudo work just fine. EDIT: And same USB device ID as you as well.
I had the same problem, I used to use Windows 10 and used fingerprint authorization. After I switched to Ubuntu 22.04.4 LTS (Jammy Jellyfish), the fingerprints were registered normally, but the fingerprint login did not work in the login window. I tried to reset according to the author's instructions:
At some of the above points you may get a 'device busy' error, depending on how systemctl plays along. Kill offending processes if necessary, or re-run the systemctl stop python3-validity command, in case it has automatically been restarted, or or kill other offending processes.
but I ran into a problem with the USB being busy. So I went into Windows, which I had next to Ubuntu on the same system and followed the steps as in the screenshot to remove any previous finger registrations.
I had the same problem, I used to use Windows 10 and used fingerprint authorization. After I switched to Ubuntu 22.04.4 LTS (Jammy Jellyfish), the fingerprints were registered normally, but the fingerprint login did not work in the login window. I tried to reset according to the author's instructions:
At some of the above points you may get a 'device busy' error, depending on how systemctl plays along. Kill offending processes if necessary, or re-run the systemctl stop python3-validity command, in case it has automatically been restarted, or or kill other offending processes.
but I ran into a problem with the USB being busy. So I went into Windows, which I had next to Ubuntu on the same system and followed the steps as in the screenshot to remove any previous finger registrations.
Activity
[-][Ubuntu 22.04] Enroll works, verify does not, no error[/-][+][Ubuntu 22.04] Enroll works, verify does not, no error (X1 Yoga 2nd 138a:0097)[/+]khatfull commentedon Mar 27, 2024
I had some goofy problems on a T470 that I just setup. I could enroll just fine but then never validate, login or sudo. What appears to have fixed it is using the instructions to factory reset the firmware. This was on a machine originally setup with Windows 10 and the fingerprint reader, then reloaded with Ubuntu 22.04 (no dual boot). systemctl status python3-validity did not report errors but since I did have the sensor configured and fingerprints enrolled under Windows I took a flyer at the reset. Now login and sudo work just fine. EDIT: And same USB device ID as you as well.
mikpotik commentedon Aug 17, 2024
I had the same problem, I used to use Windows 10 and used fingerprint authorization. After I switched to Ubuntu 22.04.4 LTS (Jammy Jellyfish), the fingerprints were registered normally, but the fingerprint login did not work in the login window. I tried to reset according to the author's instructions:
$ sudo systemctl stop python3-validity
$ sudo validity-sensors-firmware
$ sudo python3 /usr/share/python-validity/playground/factory-reset.py
At some of the above points you may get a 'device busy' error, depending on how systemctl plays along. Kill offending processes if necessary, or re-run the systemctl stop python3-validity command, in case it has automatically been restarted, or or kill other offending processes.
$ sudo systemctl start python3-validity
$ fprintd-enroll
but I ran into a problem with the USB being busy. So I went into Windows, which I had next to Ubuntu on the same system and followed the steps as in the screenshot to remove any previous finger registrations.
Windows 10:
arya6000 commentedon Nov 2, 2025
I had the same problem, this fixed it