You are not logged in.
Hey,
I recently got a refurbished Thinkpad T440, and have been trying to get sudo to work with fprint (as per https://wiki.archlinux.org/index.php/Fprint), and the sensor is being extremely slow.
For example, while enrolling, it took anywhere from 30 seconds to 1 minute to get to the next enrollment step, and sudo times out the verification.
The sensor itself is listed as supported at https://fprint.freedesktop.org/supported-devices.html.
journalctl doesn't show anything of interest, what would be the next steps in figuring out what's causing this slowness?
Thanks,
George
Last edited by gtsatsis (2020-09-04 16:12:54)
Offline
Are you using Fingerprint GUI?
Offline
Are you using Fingerprint GUI?
Yes, and no; I do have it installed, and it is really slow as well, but I used
fprintd-enrollto set the fingerprint up this time.
Offline
Odd, I'm on a T440S as well, i7, 12gb, 5.4.61 Kernel, Bus 001 Device 003: ID 138a:0017 Validity Sensors, Inc. VFS 5011 fingerprint sensor
lightdm-1:1.30.0-4, fprintd-1.90.1-1, fingerprint-gui 1.09-7
fingerprint-gui -d will allow you to debug
My pam settings for fingerprint-gui are as follows, though it has nothing to do with the register scanning
/etc/pam.d/lightdm
auth sufficient pam_fingerprint-gui.so
/etc/pam.d/su
auth sufficient pam_fingerprint-gui.so
/etc/pam.d/sudo
auth sufficient pam_fingerprint-gui.so
Offline
Odd indeed, here's the output from journalctl while validating my fingerprint using fingerprint-gui -d:
Sep 05 04:16:57 ultithonk fingerprint-gui[16440]: A fingerprint for Right Index exists already.
Sep 05 04:16:59 ultithonk fingerprint-gui[16440]: Clicked "Verify".
Sep 05 04:16:59 ultithonk fingerprint-gui[16440]: Swipe finger at vfs5011.
Sep 05 04:16:59 ultithonk fingerprint-gui[16440]: Thread started.
Sep 05 04:16:59 ultithonk fingerprint-gui[16440]: Starting verify.
Sep 05 04:17:00 ultithonk kernel: usb 2-6: reset full-speed USB device number 3 using xhci_hcd
Sep 05 04:17:00 ultithonk fingerprint-gui[16440]: Need 1 stages.
Sep 05 04:17:00 ultithonk fingerprint-gui[16440]: Verify waiting...
Sep 05 04:17:08 ultithonk root[16495]: ACPI action undefined: PNP0C0A:01
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Verify: have image.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: FP_VERIFY_MATCH.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: FP_DEV_CLOSE.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Verify OK
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Verify result FP_VERIFY_MATCH.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Thread ended normally.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Verify complete.
Sep 05 04:17:36 ultithonk fingerprint-gui[16440]: Fingerprint was verified.The only thing I can see out of the ordinary is the undefined ACPI action (which I was unable to reproduce).
At this point my only theory is that fprintd is waiting some amount of time by itself, but where would that even be configured.
Offline
So the pause is right after the ACPI action undefined: PNP0C0A:01 but your saying that it doesn't show in the log every time?
Do you have any weird ACPI actions set for the fingerprint scanner? /etc/acpi/actions/
Offline
So the pause is right after the ACPI action undefined: PNP0C0A:01 but your saying that it doesn't show in the log every time?
Do you have any weird ACPI actions set for the fingerprint scanner? /etc/acpi/actions/
There are no ACPI actions set at all; This must've been something unrelated to the fingerprint scanner.
Offline
Here is my journalctl log from a test I just did (sorry took a few unsuccessful swipes from the log, thats why there is a 6 second gap at 12:14:06). Key difference seems to be I'm using pam modules.
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Started.
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Proprietary lib "libbsapi.so.4.3>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Libfprint initialized.
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Libbsapi initialized.
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Devices initialized.
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Intel Corp./un>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Linux Foundati>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Silicon Motion>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Linux Foundati>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Chicony Electr>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Intel Corp./un>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Validity Senso>
Sep 06 12:13:53 myarch fingerprint-gui[42133]: Found USB device: Linux Foundati>
Sep 06 12:13:54 myarch fingerprint-gui[42133]: No devices found by libbsapi.
Sep 06 12:13:54 myarch fingerprint-gui[42133]: initializing libfprint device (v>
Sep 06 12:13:54 myarch fingerprint-gui[42133]: Added vfs5011.
Sep 06 12:13:54 myarch fingerprint-gui[42133]: Current device set to 0 -- vfs50>
Sep 06 12:13:54 myarch fingerprint-gui[42133]: Current device set to 0 -- vfs50>
Sep 06 12:13:58 myarch kernel: usb 1-6: reset full-speed USB device number 3 us>
Sep 06 12:14:02 myarch fingerprint-gui[42133]: Testing service "sudo"
Sep 06 12:14:02 myarch fingerprint-gui[42133]: stopping device.
Sep 06 12:14:02 myarch fingerprint-gui[42133]: exit libfprint.
Sep 06 12:14:02 myarch fingerprint-gui[42133]: terminating libbsapi.
Sep 06 12:14:02 myarch fingerprint-gui[42133]: Devices released.
Sep 06 12:14:02 myarch fingerprint-gui[42133]: PAM_CALLBACK, waiting.
Sep 06 12:14:05 myarch kernel: usb 1-6: reset full-speed USB device number 3 us>
Sep 06 12:14:06 myarch fingerprint-helper[42148]: Not running as root (need pke>
Sep 06 12:14:06 myarch pkexec[42153]: pam_unix(polkit-1:session): session opene>
Sep 06 12:14:06 myarch audit[42153]: USER_START pid=42153 uid=1000 auid=1000 se>
Sep 06 12:14:06 myarch pkexec[42153]: dale: Executing command [USER=root] [TTY=>
Sep 06 12:14:06 myarch kernel: audit: type=1105 audit(1599408846.219:180): pid=>
Sep 06 12:14:06 myarch fingerprint-helper[42148]: Not running as root (need pke>
Sep 06 12:14:06 myarch pkexec[42156]: pam_unix(polkit-1:session): session opene>
Sep 06 12:14:06 myarch audit[42156]: USER_START pid=42156 uid=1000 auid=1000 se>
Sep 06 12:14:06 myarch pkexec[42156]: dale: Executing command [USER=root] [TTY=>
Sep 06 12:14:06 myarch kernel: audit: type=1105 audit(1599408846.239:181): pid=>
Sep 06 12:14:06 myarch fingerprint-gui[42133]: Fifo opened: 20
Sep 06 12:14:06 myarch fingerprint-gui[42133]: Read from fifo: _nOrMaL_Authenti>
Sep 06 12:14:12 myarch kernel: usb 1-6: reset full-speed USB device number 3 us>
Sep 06 12:14:12 myarch fingerprint-gui[42133]: Read from fifo: _aLiVe_
Sep 06 12:14:13 myarch fingerprint-gui[42133]: Read from fifo: _aLiVe_
Sep 06 12:14:13 myarch fingerprint-gui[42133]: Read from fifo: _aLiVe_
Sep 06 12:14:14 myarch fingerprint-gui[42133]: Read from fifo: _aLiVe_
Sep 06 12:14:14 myarch fingerprint-gui[42133]: Read from fifo: _aLiVe_
Sep 06 12:14:15 myarch fingerprint-gui[42133]: Read from fifo: _bOlD_OK
Sep 06 12:14:15 myarch fingerprint-gui[42133]: Read from fifo: _aUtH_
Sep 06 12:14:15 myarch fingerprint-gui[42133]: Received AUTH message
Sep 06 12:14:15 myarch fingerprint-gui[42133]: Caught line input.
Sep 06 12:14:15 myarch fingerprint-gui[42133]: PAM_CALLBACK return PAM_SUCCESS.Offline
I think ive encountered the same issue today. im using thinkpad t460 and it has the same validity sensor installed. first it all work fine but after i tried to use my finger print to login it became slow. i tried to do `fprintd-delete` but it failed with reply saying device already opened.
I feel like my screen lock app were still using the fingerprint hardware so it got jammed or what.
Offline