Fingerprint scanner installation!

mabox · 2021-07-02 05:05:20

Hello All,
I would like to be able to unlock my archlinux with my finger. It is not a notebook.
I have looked around and currently decided on the finger scanner from Xystec which is also listed on the fprint compatibility list with "04f3:0c3d ElanTech Fingerprint Sensor".
My desktop environment is GNOME 40.

The finger scanner is also recognized by the system:

[root@arch ~]# lsusb
Bus 001 Device 008: ID 04f3:0c3d Elan Microelectronics Corp. ELAN:Fingerprint

Because of the wiki article I have now tried to set up the software Fprint.
I skipped the "Login Configuration" listed in the wiki because I use GDM and it says that you can skip the section.

My problem now is that there is no option in GDM to unlock with the finger, also in the Gnome settings there is no option anywhere and when I run fprint-enroll I get "No device abailable".

[root@arch ~]# fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available

The following command, which I often read about in my research, does not work either:

[root@arch ~]# pam-auth-update
-bash: pam-auth-update: Kommando nicht gefunden.

As you can see, i am not very familiar with this topic. Maybe someone has the same problem and already a solution?
If another fingerprint scanner is needed, that's no problem either, I can gladly replace this one.
But actually mine is recognized with lsusb. A configuration should therefore possibly be possible?

Here is the output of journalctl:

[root@arch bin]# systemctl status fprintd.service 
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Jun 26 09:07:43 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 09:28:25 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 09:28:25 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 09:28:56 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 10:10:17 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 10:10:17 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 10:10:47 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
[root@arch bin]# systemctl start fprintd.service 

[root@arch bin]# systemctl status fprintd.service 
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: active (running) since Sat 2021-06-26 13:40:03 CEST; 3s ago
       Docs: man:fprintd(1)
   Main PID: 10500 (fprintd)
      Tasks: 5 (limit: 18919)
     Memory: 1.5M
        CPU: 45ms
     CGroup: /system.slice/fprintd.service
             └─10500 /usr/lib/fprintd

Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.

[root@arch bin]# journalctl -u fprintd.service
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.

So fprint service didn't run at first, so started it now, but doesn't change anything. Error message at "frpintd-enroll" is still the same.
After a while the service is "deactivated" again???

[root@arch bin]# systemctl status fprintd.service 
○ fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Jun 26 10:10:47 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:38:42 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:38:42 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:39:13 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:40:03 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:40:03 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:40:33 arch systemd[1]: fprintd.service: Deactivated successfully.
Jun 26 13:42:21 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jun 26 13:42:21 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jun 26 13:42:51 arch systemd[1]: fprintd.service: Deactivated successfully.

I hope someone can help me :-)

Many greetings
mabo

schard · 2021-07-02 13:26:41

Maybe check whether there's a firmware update available:
https://askubuntu.com/questions/1307127 … ot-working

# fwupdmgr enable-remote lvfs-testing
# fwupdmgr refresh --force
# fwupdmgr update
# fwupdmgr disable-remote lvfs-testing

mabox · 2021-07-02 13:57:59

unfortunately does not seem so

[root@arch ~]# fwupdmgr enable-remote lvs-testing
No remote 'lvs-testing' found in search paths
[root@arch ~]# fwupdmgr refresh --force
Updating lvfs
Herunterladen …          [***************************************]
Herunterladen …          [***************************************]
Successfully downloaded new metadata: 0 local devices supported
[root@arch ~]# fwupdmgr update
Devices with no available firmware updates: 
 • BCM20702A0
 • SanDisk SDSSDH3500G
 • SanDisk SDSSDH3500G
 • System Firmware
 • UEFI dbx
 • Unifying Receiver
No updatable devices
[root@arch ~]# fwupdmgr disable-remote lvs-testing
No remote 'lvs-testing' found in search paths

Piri · 2021-07-02 14:14:27

mabox wrote:

unfortunately does not seem so

[root@arch ~]# fwupdmgr enable-remote lvs-testing
No remote 'lvs-testing' found in search paths

I think you missed the 'f' in lvfs-testing

mabox · 2021-07-02 14:24:41

Thank you :-)

Is this the fingerprint? UEFI? I don't think so......

[root@arch ~]# fwupdmgr enable-remote lvfs-testing
╔══════════════════════════════════════════════════════════════════════════════╗
║ Enable new remote?                                                           ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ Der LVFS ist ein kostenloser Dienst, der als unabhängige juristische         ║
║ Person arbeitet und keine Verbindung zu Arch Linux hat. Möglicherweise hat   ║
║ Ihr Lieferant eine der Firmware-Aktualisierungen nicht auf Kompatibilität    ║
║ mit Ihrem System oder angeschlossenen Geräten überprüft. Die gesamte         ║
║ Firmware wird nur vom Originalhersteller zur Verfügung gestellt.             ║
║ Die Aktivierung dieser Funktionalität erfolgt auf eigene Gefahr, d.h. Sie    ║
║ müssen sich bei Problemen, die durch diese Aktualisierungen verursacht       ║
║ werden, an Ihren Erstausrüster wenden. Nur Probleme mit dem                  ║
║ Aktualisierungsprozess selbst sollten unter https://bugs.archlinux.org/      ║
║ eingereicht werden.                                                          ║
╚══════════════════════════════════════════════════════════════════════════════╝

Agree and enable the remote? [Y|n]: Y
Authentifizierung …      [-                                      ]
Authentifizierung …      [***************************************]
Do you want to refresh this remote now? (Erfordert Internetverbindung) [Y|n]: Y
Herunterladen …          [***************************************]
Herunterladen …          [***************************************] Weniger als eine Minute verbleiben…

Successfully enabled and refreshed remote
[root@arch ~]# fwupdmgr refresh --force
Updating lvfs-testing
Herunterladen …          [***************************************]
Updating lvfs
Herunterladen …          [***************************************]
Successfully downloaded new metadata: 2 local devices supported
[root@arch ~]# fwupdmgr update
Devices with no available firmware updates: 
 • BCM20702A0
 • SanDisk SDSSDH3500G
 • SanDisk SDSSDH3500G
 • System Firmware
╔══════════════════════════════════════════════════════════════════════════════╗
║ Upgrade UEFI dbx from 13 to 77?                                              ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ This updates the dbx to the latest release from Microsoft.                   ║
║ UEFI dbx and all connected devices may not be usable while updating.         ║
╚══════════════════════════════════════════════════════════════════════════════╝

Perform operation? [Y|n]:

mabox · 2021-07-03 07:31:11

After updating arch, I now actually see in GNOME's user settings that I can enable the fingerprint and enroll a finger. However, this failed and now I get the following messages....

journalctl -u fprintd.service

Jul 03 09:22:09 arch systemd[1]: Starting Fingerprint Authentication Daemon...
Jul 03 09:22:09 arch systemd[1]: Started Fingerprint Authentication Daemon.
Jul 03 09:22:19 arch fprintd[2515]: Failed to clear storage before first enrollment: Device has no storage.
Jul 03 09:22:19 arch fprintd[2515]: Device reported an error during identify for enroll: Calibration failed!
Jul 03 09:22:41 arch fprintd[2515]: Failed to clear storage before first enrollment: Device has no storage.
Jul 03 09:22:43 arch fprintd[2515]: Device reported an error during identify for enroll: Calibration failed!
Jul 03 09:22:56 arch fprintd[2515]: Failed to clear storage before first enrollment: Device has no storage.
Jul 03 09:22:56 arch fprintd[2515]: Device reported an error during identify for enroll: The driver encountered a protocol error with the device.
Jul 03 09:23:02 arch fprintd[2515]: Authorization denied to :1.93 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:23:09 arch fprintd[2515]: Authorization denied to :1.93 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:23:43 arch fprintd[2515]: Authorization denied to :1.100 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:24:06 arch fprintd[2515]: Authorization denied to :1.93 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:24:15 arch fprintd[2515]: Authorization denied to :1.105 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:24:30 arch fprintd[2515]: Authorization denied to :1.93 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:25:35 arch fprintd[2515]: Authorization denied to :1.108 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed
Jul 03 09:25:40 arch fprintd[2515]: Authorization denied to :1.109 to call method 'Claim' for device 'ElanTech Fingerprint Sensor': Device was already claimed

[root@arch ~]# fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.AlreadyInUse: Device was already claimed

lsusb show this now.

[root@arch ~]# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 007: ID 04f3:0c3d Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 0b05:17cb ASUSTek Computer, Inc. Broadcom BCM20702A0 Bluetooth
Bus 001 Device 003: ID 0e8d:1887 MediaTek Inc. Slim Portable DVD Writer
Bus 001 Device 002: ID 04b8:1129 Seiko Epson Corp. ET-4750 [WorkForce ET-4750 EcoTank All-in-One]
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Does anyone have any ideas? I think that now the hardware has been recognized correctly and I just need to teach a finger.
When I start arch I get the messages that the fingerprint login did not work and then I get locked. But I have not yet learned a finger.

schard · 2021-07-03 10:24:22

Try installing usb_modeswitch.

mabox · 2021-07-03 10:45:25

Ok and then? I have installed it but everything behaves as before?
When I teach in a finger, I immediately receive an error.

Is it possible that the UEFI Update will help? See thread #5 above?

Last edited by mabox (2021-07-03 11:15:37)

mabox · 2021-07-03 11:38:08

I uninstalled and installed a few times (fprint) and now i could learn a finger....

[mabox@arch ~]$ fprintd-enroll
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-retry-scan
Enroll result: enroll-retry-scan
Enroll result: enroll-retry-scan
Enroll result: enroll-stage-passed
Enroll result: enroll-retry-scan
Enroll result: enroll-stage-passed
Enroll result: enroll-stage-passed
Enroll result: enroll-completed

Unfortunately the finger is then not recognized at login :-(

And now it's back to the way it was before. I can't teach in fingers again and get errors....

[mabo@arch ~]$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
Enroll result: enroll-unknown-error

Last edited by mabox (2021-07-03 11:48:58)

mabox · 2021-07-04 10:53:02

Ok so the fingerprint is set up, but it is not recognized at login or with fprintd-verify.

[root@arch ~]# ll /var/lib/fprint/mabox/elan/0/7 
-rw-r--r-- 1 root root 451  3. Jul 16:51 /var/lib/fprint/mabo/elan/0/7

[mabox@arch ~]$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-no-match (done)

Lone_Wolf · 2021-07-04 12:40:05

mabox wrote:

I skipped the "Login Configuration" listed in the wiki because I use GDM and it says that you can skip the section.

Try revisiting that section and setup things for pam so it will work with any login method .
Also make sure you have processed all .pacnew files in /etc/pam.d folder .

mabox · 2021-07-10 06:12:14

This has not changed anything, I still have no success in verifying my learned finger, .pacnew files I do not have.

[mabo@arch ~]$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify started!
Verifying: right-index-finger
Verify result: verify-no-match (done)

Has anyone here successfully managed a USB finger scanner on the arch?

nomasteryoda · 2022-10-07 14:43:44

I had this working perfectly from May 2022 until Oct 3. I don't know what happened with it, but now this fails to authenticate with fingerprints.

 
Oct 07 10:29:31 laptop42 fprintd[2094]: Device reported finger status change: FP_FINGER_STATUS_NEEDED
Oct 07 10:29:31 laptop42 fprintd[2094]: Finger present 0
Oct 07 10:29:31 laptop42 fprintd[2094]: Finger needed 1
Oct 07 10:29:31 laptop42 fprintd[2094]: Sent identification request
Oct 07 10:29:31 laptop42 fprintd[2094]: Sent identification request
Oct 07 10:29:33 laptop42 fprintd[2094]: [elanmoc2] IDENTIFY_NUM_STATES entering state 3
Oct 07 10:29:33 laptop42 fprintd[2094]: Device reported finger status change: FP_FINGER_STATUS_PRESENT
Oct 07 10:29:33 laptop42 fprintd[2094]: Finger present 1
Oct 07 10:29:33 laptop42 fprintd[2094]: Finger needed 0
Oct 07 10:29:33 laptop42 fprintd[2094]: Identified finger 3; requesting finger info
Oct 07 10:29:33 laptop42 fprintd[2094]: [elanmoc2] IDENTIFY_NUM_STATES entering state 4
Oct 07 10:29:33 laptop42 fprintd[2094]: Device reported finger status change: FP_FINGER_STATUS_NONE
Oct 07 10:29:33 laptop42 fprintd[2094]: Finger present 0
Oct 07 10:29:33 laptop42 fprintd[2094]: Finger needed 0
Oct 07 10:29:33 laptop42 fprintd[2094]: Creating new print: finger 3, user id[28]: FP1-20221001-2-FEA5C64F-joe
Oct 07 10:29:33 laptop42 fprintd[2094]: Finger info with libfprint user ID
Oct 07 10:29:33 laptop42 fprintd[2094]: Identify: no match
Oct 07 10:29:33 laptop42 fprintd[2094]: Device reported identify result
Oct 07 10:29:33 laptop42 fprintd[2094]: report_verify_status: result verify-no-match
Oct 07 10:29:33 laptop42 fprintd[2094]: Device reported identify completion
Oct 07 10:29:33 laptop42 fprintd[2094]: [elanmoc2] IDENTIFY_NUM_STATES completed successfully
Oct 07 10:29:33 laptop42 fprintd[2094]: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
Oct 07 10:29:33 laptop42 fprintd[2094]: Not updating temperature model, device can run continuously!
Oct 07 10:29:33 laptop42 fprintd[2094]: identify_cb: result verify-no-match
Oct 07 10:29:33 laptop42 fprintd[2094]: Requesting authorization from :1.120 to call method 'VerifyStop' for device 'ELAN Match-on-Chip 2'
Oct 07 10:29:33 laptop42 fprintd[2094]: Authorization granted to :1.120 to call method 'VerifyStop' for device 'ELAN Match-on-Chip 2'!
Oct 07 10:29:33 laptop42 fprintd[2094]: Requesting authorization from :1.120 to call method 'Release' for device 'ELAN Match-on-Chip 2'
Oct 07 10:29:33 laptop42 fprintd[2094]: Authorization granted to :1.120 to call method 'Release' for device 'ELAN Match-on-Chip 2'!
Oct 07 10:29:33 laptop42 fprintd[2094]: Closing device
Oct 07 10:29:33 laptop42 fprintd[2094]: Cancelling any ongoing requests
Oct 07 10:29:33 laptop42 fprintd[2094]: Device reported close completion

LEAVING this post here... in the hopes it helps someone else ... or myself find the answer again should it happen. (and no, there is no Windows on this box).

RESOLVED

0. Rebooted my HP X360 into the BIOS, changed the delete fingerprints on reboot.
1. Logged into system using password as no fingerprints exist.
2. fprint-enroll - added fingerprints
3. Rebooted
4. FTW! - Success! - Logged into system with fingerprints.
5. WHY??? I didn't change the BIOS and didn't even know that option existed. This thing has been authenticating for months with fingerprints.

Last edited by nomasteryoda (2022-10-07 19:25:58)

Arch Linux

#1 2021-07-02 05:05:20

Fingerprint scanner installation!

#2 2021-07-02 13:26:41

Re: Fingerprint scanner installation!

#3 2021-07-02 13:57:59

Re: Fingerprint scanner installation!

#4 2021-07-02 14:14:27

Re: Fingerprint scanner installation!

#5 2021-07-02 14:24:41

Re: Fingerprint scanner installation!

#6 2021-07-03 07:31:11

Re: Fingerprint scanner installation!

#7 2021-07-03 10:24:22

Re: Fingerprint scanner installation!

#8 2021-07-03 10:45:25

Re: Fingerprint scanner installation!

#9 2021-07-03 11:38:08

Re: Fingerprint scanner installation!

#10 2021-07-04 10:53:02

Re: Fingerprint scanner installation!

#11 2021-07-04 12:40:05

Re: Fingerprint scanner installation!

#12 2021-07-10 06:12:14

Re: Fingerprint scanner installation!

#13 2022-10-07 14:43:44

Re: Fingerprint scanner installation!

Board footer