Enroll fingerprints of t460p jammy with windows dual boot
default-student opened this issue · 3 comments
Dual boot windows
install uunicorn/python-validity#129 (comment)
according to the comment
boot into windows
enroll in windows
boot into linux
check that sudo systemctl status python3-validity.service throws no error
● python3-validity.service - python-validity driver dbus service
Loaded: loaded (/lib/systemd/system/python3-validity.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-06-25 13:23:53 CEST; 17min ago
Main PID: 1496 (python3)
Tasks: 3 (limit: 9059)
Memory: 31.5M
CPU: 363ms
CGroup: /system.slice/python3-validity.service
└─1496 python3 /usr/lib/python-validity/dbus-service --debug
Jun 25 13:40:19 r4-t460p python3[1496]: DEBUG:root:In EnrollStart right-index-finger for {r4}
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:In ListEnrolledFingers r4
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:>tls> 17: 4b00000b0053746757696e64736f7200
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:>cmd> 17030300504129a12eba3cb867bfad483ca465af8748cc6f5475b0ad87>
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:<cmd< 170303005025a0a63baa2cf6043fbce1645bf27b8fca928323356b7819>
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:<tls< 17: 0000030001000b00000005004c0053746757696e64736f7200
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:>tls> 17: 4a000003004c00030000001c000000010500000000000515000000>
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:>cmd> 17030300904eca1f3e15ae2a0373598cd8957c51f562e2dc9033104b69>
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:<cmd< 170303004039f93ec755a6d765c4d59798fec69cb199b606c8fe473e5e>
Jun 25 13:40:40 r4-t460p python3[1496]: DEBUG:root:<tls< 17: b304
uninstall
sudo apt remove open-fprintd fprintd-clients python3-validity
install
sudo apt install libfprint-2-tod-vfs0090
(on jammy modify sudo nano /etc/apt/sources.list.d/3v1n0-ubuntu-libfprint-vfs0090-jammy.list replace jammy with focal)
sudo apt install fprintd
check service
sudo systemctl start fprintd.service
sudo systemctl status fprintd.service
● fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: active (running) since Tue 2024-06-25 13:56:11 CEST; 17s ago
Docs: man:fprintd(1)
Main PID: 4997 (fprintd)
Tasks: 5 (limit: 9059)
Memory: 2.1M
CPU: 205ms
CGroup: /system.slice/fprintd.service
└─4997 /usr/libexec/fprintd
Jun 25 13:56:11 r4-t460p systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 25 13:56:11 r4-t460p systemd[1]: Started Fingerprint Authentication Daemon.
Jun 25 13:56:11 r4-t460p fprintd[4997]: libusb: error [udev_hotplug_event] ignoring udev action change
Jun 25 13:56:11 r4-t460p fprintd[4997]: libusb: error [udev_hotplug_event] ignoring udev action change
Jun 25 13:56:13 r4-t460p fprintd[4997]: Authorization denied to :1.102 to call method 'Release' for device 'Validit>
check in system settings or with fprintd-enroll
other things to check fprintd-list
fprintd-list r4
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
Fingerprints for user r4 on Validity VFS0090 (press):
- #0: right-index-finger
add them for screen unlock and sudo like this:
https://unix.stackexchange.com/questions/655203/how-do-i-implement-fprintd-into-login-in-kubuntu
sudo apt install -y fprintd libpam-fprintd
sudo pam-auth-update
sorry for the messy write up, but i think it should be documented
do note that there are further issues on linux with finderprints.
kubuntu with sddm cant login when having the fingerprint activated using pam-auth-update.
check https://askubuntu.com/questions/1307437/can-not-login-to-sddm-using-fingerprint-on-kubuntu-20-10