You are not logged in.
Hi everyone, I just installed Arch on my ThinkPad T14s AMD Gen 1 laptop, and I'm trying to set up fingerprint authentication. At first, I simply followed the fprint wiki article. I double checked my device using `lsusb`. Here's the device info I got:
Bus 006 Device 002: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint ReaderThis is listed in the libfprint supported devices so I thought I was good to go. I installed `fprint` normally, however when I went to enroll my fingerprint through GNOME settings, it gave me this error:
Failed to claim fingerprint device Synaptic Sensors: the device is already claimed by another processA similar error message was printed when I tried running `fprintd-enroll` through the terminal. Searching up this error message brings up many help forums such as the following:
https://unix.stackexchange.com/question … the-device
I tried installing and running fwupd, but there was nothing to install.
https://askubuntu.com/questions/1231967 … focal-fosa
The answers all tell me to install testing firmware, but the question is over a year old, and the suggested firmware are now stable. I would expect that fwupd already has these installed, and indeed when I run `fwupdmgr get-updates` it shows that Prometheus already has the latest available firmware version.
https://bbs.archlinux.org/viewtopic.php?id=262476
I disabled Predesktop Authentication and reset the fingerprint in the BIOS, but the error persists. Besides, the gitlab issue referenced is marked as solved, so I would expect fprint to have resolved this automatically.
https://askubuntu.com/questions/878072/ … dy-claimed
I ran `systemctl stop fprint.service` and retried enrolling through GNOME, but it didn't work.
Finally, I tried looking at journalctl for more details, and I did find some different error messages, though I don't know if this helps:
Jul 02 11:27:29 tiramisu systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 02 11:27:30 tiramisu systemd[1]: Started Fingerprint Authentication Daemon.
Jul 02 11:27:54 tiramisu fprintd[951]: Device asked for more prints than we are providing.
Jul 02 11:27:54 tiramisu fprintd[951]: Device reported an error during identify for enroll: Unexpected index
Jul 02 11:27:57 tiramisu fprintd[951]: Authorization denied to :1.87 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jul 02 11:28:26 tiramisu fprintd[951]: Authorization denied to :1.87 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jul 02 11:29:00 tiramisu fprintd[951]: Authorization denied to :1.106 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jul 02 11:30:48 tiramisu fprintd[951]: Authorization denied to :1.87 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jul 02 12:01:27 tiramisu fprintd[951]: Authorization denied to :1.87 to call method 'Claim' for device 'Synaptics Sensors': Device was already claimed
Jul 02 12:02:26 tiramisu systemd[1]: fprintd.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Jul 02 12:02:53 tiramisu fprintd[951]: Failed to get name: net.reactivated.FprintAny other ideas?
Last edited by jc65536 (2021-07-14 20:44:59)
Offline
I have the same device, so maybe I can assist. Since your post is already a few days old: Is this still an issue?
I tried installing and running fwupd, but there was nothing to install.
https://askubuntu.com/questions/1231967 … focal-fosa
The answers all tell me to install testing firmware, but the question is over a year old, and the suggested firmware are now stable. I would expect that fwupd already has these installed, and indeed when I run `fwupdmgr get-updates` it shows that Prometheus already has the latest available firmware version.
I remember that I had to install a firmware update to get it working. Maybe a stupid question but did you run `fwupdmgr refresh` before running `fwupdmgr get-updates`?
Please run `fwupdmgr get-devices`. What is the shown firmware version? For me it looks as follows:
├─Prometheus:
│ Device ID: 50efef912094e784a03628350441f6927c4920b0
│ Zusammenfassung: Fingerprint reader
│ Current version: 10.01.3273255
│ Vendor: Synaptics (USB:0x06CB)
│ Install Duration: 2 seconds
│ Serial Number: ###############
│ GUIDs: ############### ← USB\VID_06CB&PID_00BD&REV_0000
│ ############### ← USB\VID_06CB&PID_00BD
│ Device Flags: • Updatable
│ • Supported on remote server
│ • Cryptographic hash verification is availableNotice that the firmware version is different from the LVFS entry you have linked in your post. For some reason I have a testing firmware installed: https://fwupd.org/lvfs/devices/com.syna … D.firmware
I can't remember installing a testing version on purpose. Maybe this was part of a Lenovo BIOS update.
Offline
I'd like to chime in here with my recent-install Lenovo Thinkpad X13 Gen 1 (Intel). I have the same fingerprint device with fully updated firmware (fwupdmgr says 10.01.3273255), I've turned of Pre-Desktop Authentication, and I've cleared the fingerprint data through UEFI, and I'm getting the exact same error messages as the OP. I did have Windows previously installed on this laptop with fingerprint authentication, so it could be that (even though I've cleared the data from the device), though I'd like some insight as I'm not very well versed on fingerprint reader implementation on Linux.
Here's some command outputs if they're needed:
lsusb
Bus 001 Device 004: ID 06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Readerfwupdmgr get-devices
─Prometheus:
│ Device ID: d432baa2162a32c1554ef24bd8281953b9d07c11
│ Summary: Fingerprint reader
│ Current version: 10.01.3273255
│ Vendor: Synaptics (USB:0x06CB)
│ Install Duration: 2 seconds
│ GUIDs:
│ Device Flags: • Updatable
│ • Supported on remote server
│ • Cryptographic hash verification is available
│ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-disconnectedjournalctl -u fprintd.service
Jul 08 23:47:18 ArchThinkpad systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 08 23:47:18 ArchThinkpad systemd[1]: Started Fingerprint Authentication Daemon.
Jul 08 23:47:21 ArchThinkpad fprintd[719]: Device asked for more prints than we are providing.
Jul 08 23:47:21 ArchThinkpad fprintd[719]: Device reported an error during identify for enroll: Unexpected indexAny help is greatly appreciated, and I hope I can be of some use to help troubleshoot this issue
Thanks!
Offline
I had the same issue.
It seems that there is a bug in fprintd package itself (https://bugs.archlinux.org/task/71431)
To anyone affected and who has that latest firmware on fingerprint reader I recommend getting an older version of fprintd for the time being
https://archive.archlinux.org/packages/ … kg.tar.zst
To install, move into directory where you've downloaded the old version of fprintd and execute
pacman -U fprintd-1.90.9-1-x86_64.pkg.tar.zstAlso one should probably configure pacman to not update fprintd to new version for the time being
by listing the package in pacman.conf under IgnorePkg parameter
Offline
Hi,
This solved my long time issue with fingerprint reader...thanks
Why did Bodhidharma come from the west?
Offline