Sample Header Ad - 728x90

Unix & Linux Stack Exchange

Q&A for users of Linux, FreeBSD and other Unix-like operating systems

Latest Questions

6 votes
2 answers
11509 views
Fingerprint reader on Asus Zenbook
asus zorin fingerprint zenbook
So I have `ZorinOS` installed on my `ASUS ZenBook UX330UA-AH54`, however, `FingerprintGUI` shows my fingerprint sensor (`Elantech` I think) as an unknown device. Is there any custom software or fixes that can be used to get my laptop to pickup the `fingerprint sensor`?
So I have ZorinOS installed on my ASUS ZenBook UX330UA-AH54, however, FingerprintGUI shows my fingerprint sensor (Elantech I think) as an unknown device. Is there any custom software or fixes that can be used to get my laptop to pickup the fingerprint sensor?
Spectre216 (61 rep)
Oct 6, 2017, 01:10 PM • Last activity: Jul 11, 2025, 01:38 PM
11 votes
3 answers
6985 views
Use fingerprint reader for everything but first login
linux-mint pam fingerprint
I want to make efficient use of the fingerprint reader on my laptop. I was able to configure fingerprint reading through `fprint` and PAM (using the steps described in the second comment [here][1]), but I've encountered a small problem. When logging in with the fingerprint reader the GNOME keyring i...
I want to make efficient use of the fingerprint reader on my laptop. I was able to configure fingerprint reading through fprint and PAM (using the steps described in the second comment here ), but I've encountered a small problem. When logging in with the fingerprint reader the GNOME keyring isn't unlocked. Now I understand that this is this way because fprintand the keyring have no support for hardware-based keystore unlocking like for example Windows Hello does. I have no problem with this restriction, but it means that I have to type my password on login anyways. How I get around this right now is by waiting for 10s on the first login so the fingerprint reader times out and I get the password prompt. Then I enter the password to login and the keyring gets unlocked with the login. When I unlock my device or run sudo commands afterwards I will still use the fingerprint reader. So my question is if it is possible to configure PAM in a way that allows me to do the first login directly with the password (without waiting for the fingerprint sensor to time out) while still allowing me to unlock and run sudo commands with the fingerprint reader. I'm running Linux Mint with the Cinnamon desktop.
Emil S. (213 rep)
Sep 29, 2021, 07:39 AM • Last activity: Jul 11, 2025, 01:15 AM
1 votes
1 answers
3574 views
No Fingerprint Button in Ubuntu 19.04
ubuntu fingerprint
I've updated on Ubuntu 19.04, hoping to unlock my Acer Spin 5 with the Elantech Fingerprint Sensor (04f3: 0c03). When I go to the user settings, there is no button that I can use to add fingers.
I've updated on Ubuntu 19.04, hoping to unlock my Acer Spin 5 with the Elantech Fingerprint Sensor (04f3: 0c03). When I go to the user settings, there is no button that I can use to add fingers.
MarkusMCPEGamer (19 rep)
May 12, 2019, 09:52 AM • Last activity: Jun 23, 2025, 11:04 PM
2 votes
0 answers
59 views
How to install a firmware on Linux for a fingerprint reader?
arch-linux firmware thinkpad fingerprint
I have a Lenovo Thinkpad E15 Gen2 with a Goodix fingerprint reader and I'm trying to make it work for login on Arch Linux. I've installed `fingerprint-gui` but it's not recognized by it and I found this [Github][1] with the firmware I need. The ID of my fingerprint is `27c6:55a4`. I found the firmwa...
I have a Lenovo Thinkpad E15 Gen2 with a Goodix fingerprint reader and I'm trying to make it work for login on Arch Linux. I've installed fingerprint-gui but it's not recognized by it and I found this Github with the firmware I need. The ID of my fingerprint is 27c6:55a4. I found the firmware, made it executable with sudo chmod +x GF3268_RTSEC_APP_10041.bin and put it in /usr/lib/firmware but it's still not recognized by fingerprint-gui. How do I know if my firmware is correctly installed?
Gamix (21 rep)
Jun 20, 2025, 06:32 PM • Last activity: Jun 21, 2025, 08:45 AM
5 votes
2 answers
2178 views
How do you use a fingerprint to boot LUKS-encrypted Arch Linux?
arch-linux grub2 luks fingerprint
I'm searching for clues on how to use a fingerprint reader to unlock a LUKS-encrypted device. My hard disk uses `/dev/sda2` (encrypted with LUKS) to start the OS. I don't want to use complex passphrases because it could be forgotten by the users. How do you use a fingerprint to boot from a LUKS-encr...
I'm searching for clues on how to use a fingerprint reader to unlock a LUKS-encrypted device. My hard disk uses /dev/sda2 (encrypted with LUKS) to start the OS. I don't want to use complex passphrases because it could be forgotten by the users. How do you use a fingerprint to boot from a LUKS-encrypted device?
Micael André (445 rep)
Feb 8, 2017, 04:45 PM • Last activity: Jun 18, 2025, 11:02 AM
0 votes
1 answers
172 views
fprintd times out
authentication fingerprint
On login, `sudo` call, or any authentication attempt, the process hangs for a while, then prompts for password. Expected behavior: immediately display fingerprint prompt. Upon investigation, `fprintd-verify`, `fprintd-enroll`, `fprintd-delete`, and `fprintd-list` all time out with the following erro...
On login, sudo call, or any authentication attempt, the process hangs for a while, then prompts for password. Expected behavior: immediately display fingerprint prompt. Upon investigation, fprintd-verify, fprintd-enroll, fprintd-delete, and fprintd-list all time out with the following error: 
$ fprintd-list $USERNAME # example command
Failed to get Fprintd manager: Error calling StartServiceByName for net.reactivated.Fprint: Timeout was reached
My fingerprint sensor is supported; fprintd, fprintd-pam, and libfprint were installed from official repositories on distro install. All are configured as default when installed, with no modificatons. Running Fedora 42. This behavior was not present a week ago, when I used fprintd-enroll right-middle-finger to register a fingerprint. It developed sometime after a system upgrade from Fedora 41 to 42.
Akhil Pillai (1 rep)
Apr 23, 2025, 05:37 PM • Last activity: Apr 25, 2025, 01:51 AM
15 votes
4 answers
6593 views
How to disable fingerprint authentication when laptop lid is closed?
ubuntu systemd pam acpi fingerprint
I recently managed to make fingerprint authentication work on my laptop, thanks to the [Goodix Linux][1] [Development](https://discord.com/invite/6xZ6k34Vqg) Discord community and the GitHub users Infinytum and Michael Teuscher on the [`driver/538d` branch][2]. But after enabling fingerprint for log...
I recently managed to make fingerprint authentication work on my laptop, thanks to the Goodix Linux [Development](https://discord.com/invite/6xZ6k34Vqg) Discord community and the GitHub users Infinytum and Michael Teuscher on the driver/538d branch . But after enabling fingerprint for login with fprintd-enroll and for sudo access with sudo pam-auth-update I noticed a problem: Whenever I am using an external monitor to work, and the lid is closed, I have to wait for the fingerprint authentication to time out, before being able to type the sudo password, which causes a delay of several seconds: 
username@host:~/ron/libfprint$ sudo ls
Place your finger on the fingerprint reader
Place your finger on the reader again
Place your finger on the reader again
Place your finger on the reader again
Verification timed out
[sudo] password for username:
How can I disable fingerprint authentication when the laptop lid is closed, so I can type the sudo password without waiting for the fingerprint to time out?
user000001 (3795 rep)
Nov 22, 2021, 12:52 PM • Last activity: Apr 22, 2025, 08:15 AM
3 votes
0 answers
927 views
EgisTec 0570 Fingerprint Sensor - fprintd-enroll not working
arch-linux uefi hardware fingerprint
I have an Acer Swift 3 (SF314-57) running arch, which has an 0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor. Support for this device was just made available in the latest libfprint release (v1.92.1), so naturally I have been trying to get it working. I installed the fprintd package...
I have an Acer Swift 3 (SF314-57) running arch, which has an 0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor. Support for this device was just made available in the latest libfprint release (v1.92.1), so naturally I have been trying to get it working. I installed the fprintd package from the official arch repo, however, when I try to enroll a fingerprint, it just 'gets stuck' saying Enrolling right-index-finger finger with a blinking cursor, and no amount of trying to scan my fingerprint will get it to give any sort of indication that something is happening. The device is seen by my system and fprintd.service is running: 
$ sudo systemctl status fprintd.service
[sudo] password for mipy: 
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/usr/lib/systemd/system/fprintd.service; static)
     Active: active (running) since Sun 2021-08-08 16:04:25 AEST; 3s ago
       Docs: man:fprintd(1)
   Main PID: 7381 (fprintd)
      Tasks: 6 (limit: 18803)
     Memory: 1.6M
        CPU: 57ms
     CGroup: /system.slice/fprintd.service
             └─7381 /usr/lib/fprintd

Aug 08 16:04:24 ruby-swift314-57 systemd: Starting Fingerprint Authentication Daemon...
Aug 08 16:04:25 ruby-swift314-57 systemd: Started Fingerprint Authentication Daemon.
$ lsusb
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 003: ID 04f2:b5c5 Chicony Electronics Co., Ltd HD WebCam
Bus 003 Device 002: ID 1c7a:0570 LighTuning Technology Inc. EgisTec Touch Fingerprint Sensor
Bus 003 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The only errors I get from journalctl -f -u fprintd.service are: 
fprintd: Failed to clear storage before first enrollment: Device has no storage.
I should add that my disk has ~50GB of storage available, so the problem isn't with my disk's storage - I assume the reader's? When I build libfprint from source, using meson compile and then meson test, and try to enroll using the examples, it shows: 
This program will enroll the selected finger, unconditionally overwriting any print for the same finger that was enrolled previously. If you want to continue, press enter, otherwise hit Ctrl+C

Choose the finger to enroll:
   left thumb
   left index
   left middle
   left ring
   left little
   right thumb
   right index
   right middle
   right ring
   right little
> 6
(process:5575): libfprint-context-DEBUG: 15:21:02.406: No driver found for USB device 1D6B:0003
(process:5575): libfprint-context-DEBUG: 15:21:02.406: No driver found for USB device 04F2:B5C5
(process:5575): libfprint-context-DEBUG: 15:21:02.407: No driver found for USB device 8087:0026
(process:5575): libfprint-context-DEBUG: 15:21:02.407: No driver found for USB device 1D6B:0002
(process:5575): libfprint-context-DEBUG: 15:21:02.407: No driver found for USB device 1D6B:0003
(process:5575): libfprint-context-DEBUG: 15:21:02.407: No driver found for USB device 1D6B:0002
Selected device 0 (Egis Technology Inc. (aka. LighTuning) 0570) claimed by egis0570 driver
(process:6437): libfprint-image_device-DEBUG: 15:33:00.490: Image device open completed
(process:6437): libfprint-device-DEBUG: 15:33:00.490: Device reported open completion
(process:6437): libfprint-device-DEBUG: 15:33:00.491: Completing action FPI_DEVICE_ACTION_OPEN in idle!
Opened device. It's now time to enroll your finger.

You will need to successfully scan your right index finger 5 times to complete the process.

Scan your finger now.
(process:6437): libfprint-image_device-DEBUG: 15:33:00.492: Activating image device
(process:6437): libfprint-image_device-DEBUG: 15:33:00.492: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 0
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 1
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-image_device-DEBUG: 15:33:00.492: Image device activation completed
(process:6437): libfprint-image_device-DEBUG: 15:33:00.492: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
(process:6437): libfprint-image_device-DEBUG: 15:33:00.492: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
(process:6437): libfprint-device-DEBUG: 15:33:00.492: Device reported finger status change: FP_FINGER_STATUS_NEEDED
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.492: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.493: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.494: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.495: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.496: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.497: [egis0570] SM_STATES_NUM entering state 4
(process:6437): libfprint-image_device-DEBUG: 15:33:00.564: Image device reported finger status: off
(process:6437): libfprint-SSM-DEBUG: 15:33:00.564: [egis0570] SM_STATES_NUM entering state 5
(process:6437): libfprint-SSM-DEBUG: 15:33:00.564: [egis0570] SM_STATES_NUM entering state 1
(process:6437): libfprint-SSM-DEBUG: 15:33:00.564: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.564: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.564: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 2
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 3
(process:6437): libfprint-SSM-DEBUG: 15:33:00.565: [egis0570] SM_STATES_NUM entering state 4
(process:6437): libfprint-egis0570-DEBUG: 15:33:00.632: Finger status (picture number, mean) : 0 , 0
(process:6437): libfprint-egis0570-DEBUG: 15:33:00.632: Finger status (picture number, mean) : 1 , 0
(process:6437): libfprint-egis0570-DEBUG: 15:33:00.632: Finger status (picture number, mean) : 2 , 0
(process:6437): libfprint-egis0570-DEBUG: 15:33:00.632: Finger status (picture number, mean) : 3 , 0
(process:6437): libfprint-egis0570-DEBUG: 15:33:00.632: Finger status (picture number, mean) : 4 , 0
(process:6437): libfprint-image_device-DEBUG: 15:33:00.632: Image device reported finger status: off
And just keeps looping through the "Finger status" and "SM_STATES_NUM" bit until I kill it. When I then try using manage-prints from the examples, I get: 
This program will report the prints saved in device
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 1D6B:0003
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 04F2:B5C5
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 8087:0026
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 1D6B:0002
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 1D6B:0003
(process:7187): libfprint-context-DEBUG: 15:56:24.549: No driver found for USB device 1D6B:0002
Selected device 0 (Egis Technology Inc. (aka. LighTuning) 0570) claimed by egis0570 driver
(process:7187): libfprint-image_device-DEBUG: 15:56:24.690: Image device open completed
(process:7187): libfprint-device-DEBUG: 15:56:24.691: Device reported open completion
(process:7187): libfprint-device-DEBUG: 15:56:24.691: Completing action FPI_DEVICE_ACTION_OPEN in idle!

(process:7187): libfprint-WARNING **: 15:56:24.691: Device Egis Technology Inc. (aka. LighTuning) 0570 doesn't support storage

(process:7187): libfprint-device-WARNING **: 15:56:24.691: User destroyed open device! Not cleaning up properly!
libusb: warning [libusb_exit] application left some devices open
When I try and run fwupdmgr update, I just get: 
Devices with no available firmware updates: 
 • System Firmware
 • UEFI Device Firmware
 • UEFI dbx
 • WDC PC SN520 SDAPNUW-512G-1014
No updatable devices
Does anybody know what is going on? I feel like I am missing something obvious, but I can't figure out what.
mipy (31 rep)
Aug 16, 2021, 01:35 PM • Last activity: Mar 1, 2025, 02:53 PM
3 votes
1 answers
5648 views
How to enable fingerprint login?
fedora kde login plasma fingerprint
I have installed fedora 39 kde edition on my laptop which hasa fingerprint sensor. How can I use it for login into my desktop?
I have installed fedora 39 kde edition on my laptop which hasa fingerprint sensor. How can I use it for login into my desktop?
Dario Gallo (51 rep)
Apr 2, 2024, 07:33 PM • Last activity: Jan 31, 2025, 09:04 AM
7 votes
3 answers
2046 views
PAM fingerprint login blocks password
sudo pam gdm3 fingerprint
Is there a way to make PAM run authentication modules in parallel? For all people who use PAM this may be useful. It seems that PAM runs authentication modules in sequence and blocking. What that means for people who would like to use multiple authentication mechanisms, is that we have to have a hie...
Is there a way to make PAM run authentication modules in parallel? For all people who use PAM this may be useful. It seems that PAM runs authentication modules in sequence and blocking. What that means for people who would like to use multiple authentication mechanisms, is that we have to have a hierarchy of methods that isn't obstructive. The issue that I'm trying to solve is this - GNome keyring requires a password to unlock, but I also have pam_fprintd active... and am playing around with the face recognition camera. That means that when I login for the first time - first the pam_fprintd blocks, then face recognition blocks and only then I can type in my password. That happens with sudo as well. Which is a major PITA.
Aleksandr Panzin (171 rep)
Oct 20, 2020, 09:01 PM • Last activity: Jan 14, 2025, 04:01 PM
2 votes
0 answers
3602 views
fingerprint-gui on Linux Mint 19 "Tara" cinnamon works but not on first boot or in software center
linux-mint lvm encryption pam fingerprint
On my Lenovo Thinkpad X1 Carbon 3rd. Gen., fingerprint-gui works fine when locking the screen or requesting sudo in terminal. It doesn't work when I freshly boot up the system at first login, and it doesn't work either when installing software from the apt software center over the GUI. Is there a wa...
On my Lenovo Thinkpad X1 Carbon 3rd. Gen., fingerprint-gui works fine when locking the screen or requesting sudo in terminal. It doesn't work when I freshly boot up the system at first login, and it doesn't work either when installing software from the apt software center over the GUI. Is there a way I can change something so that this works with the fingerprint, too? I must say that I've encrypted LVM partitions running, perhaps this is a reason why it doesn't work at boot time? Attached is my pam-update-auth screen. enter image description here
sagerobert (121 rep)
Dec 13, 2018, 02:51 PM • Last activity: Dec 19, 2024, 12:12 PM
1 votes
1 answers
153 views
Use an integrated fingerprint reader on HP 6710b with linux, Fedora 41
fedora linux-kernel fingerprint
The HP 6710b laptop have an integrated fingerprint reader, how can I use it with Linux on Fedora?
The HP 6710b laptop have an integrated fingerprint reader, how can I use it with Linux on Fedora?
Cătălin George Feștilă (168 rep)
Nov 24, 2024, 01:32 PM • Last activity: Nov 28, 2024, 07:54 PM
3 votes
0 answers
96 views
Fingerprint refusing to work on Arch?
arch-linux fingerprint
I'm at my wits end trying to get my fingerprint to work on Arch. I'm using a P14s Gen 5, have enrolled and verified my fingerprint with `fprintd` successfully. I followed the Wiki to update my `/etc/pam.d/system-local-login`, `/etc/pam.d/sudo`, and several others. No matter what, though, it continue...
I'm at my wits end trying to get my fingerprint to work on Arch. I'm using a P14s Gen 5, have enrolled and verified my fingerprint with fprintd successfully. I followed the Wiki to update my /etc/pam.d/system-local-login, /etc/pam.d/sudo, and several others. No matter what, though, it continues to only use my (typed) password for login AND sudo verification. I also added myself to the input group. Am I missing something? Note that it WORKS when trying a command with su -c for whatever reason. I've included the pam.d file for that as well. (And, no, it does not work if I just copy and paste the contents of su into any of those other files.) /etc/pam.d/system-local-login: 
#%PAM-1.0
auth      sufficient pam_fprintd.so
auth      include   system-login
account   include   system-login
password  include   system-login
session   include   system-login
/etc/pam.d/sudo: 
#%PAM-1.0

auth    sufficient pam_fprintd.so
auth    include    system-auth
account include    system-auth
session include    system-auth
/etc/pam.d/su 
#%PAM-1.0
auth		sufficient	pam_fprintd.so
auth            sufficient      pam_rootok.so
# Uncomment the following line to implicitly trust users in the "wheel" group.
#auth           sufficient      pam_wheel.so trust use_uid
# Uncomment the following line to require a user to be in the "wheel" group.
#auth           required        pam_wheel.so use_uid
auth            required        pam_unix.so
account         required        pam_unix.so
session	        required        pam_unix.so
password        include         system-auth
TheProgrammer (51 rep)
Oct 19, 2024, 02:42 AM • Last activity: Oct 22, 2024, 12:52 AM
1 votes
0 answers
326 views
How to setup PAM fprint grosshack with GDM?
linux arch-linux password pam fingerprint
I was following the login configurations of [fprint - ArchWiki](https://wiki.archlinux.org/title/fprint#Login_configuration), and I wanted to use `pam-fprint-grosshack` with GDM. I couldn't find any information about it, because the wiki says at the beginning of the section "If you use GDM, the fing...
I was following the login configurations of [fprint - ArchWiki](https://wiki.archlinux.org/title/fprint#Login_configuration) , and I wanted to use pam-fprint-grosshack with GDM. I couldn't find any information about it, because the wiki says at the beginning of the section "If you use GDM, the fingerprint-option is already available in the login menu (if not add yourself to the input user group). You can skip this section!". So I tried it myself and came to this conclusion, which indeed, works: 
#%PAM-1.0

auth       required                    pam_shells.so
auth       requisite                   pam_nologin.so
auth       requisite                   pam_faillock.so      preauth

auth       sufficient                  pam_fprintd_grosshack.so
auth       sufficient                  pam_unix.so try_first_pass nullok
#auth       required                    pam_fprintd.so

auth       optional                    pam_permit.so
auth       required                    pam_env.so
auth       [success=ok default=1]      pam_gdm.so
auth       optional                    pam_gnome_keyring.so

account    include                     system-local-login

password   required                    pam_deny.so

session    include                     system-local-login
session    optional                    pam_gnome_keyring.so auto_start
My question at this point is, written this way, have I compromised the security of GDM in any way? I have never written a PAM configuration before.
Giuseppe (151 rep)
Jun 6, 2024, 01:55 PM
0 votes
1 answers
1618 views
How do I Get My Fingerprint Sensor to work with SDDM Login in NixOS (Plasma 6)
systemd nixos plasma sddm fingerprint
My fingerprint sensor works fine, in fact it works quite well except when it comes to SDDM. I use fprintd and systemd. I have looked online for solutions, one involved changing some code in a systemd service, the only problem is I use NixOS. (for those who don't know, NixOS makes most of the root fo...
My fingerprint sensor works fine, in fact it works quite well except when it comes to SDDM. I use fprintd and systemd.

I have looked online for solutions, one involved changing some code in a systemd service, the only problem is I use NixOS. (for those who don't know, NixOS makes most of the root folder read only for the purpose of making everything editable from one file). I don't know how to change an existing service inside of NixOS.

to replicate my situation I have a fresh install of NixOS plasma5 from Here . I then moved to the unstable channel and upgraded my system to plasma6 with this guid . and lastly I enabled fprintd. for my sensor I didn't need to specify any drivers but your experience may vary.

Does anyone know how to fix this? and if not, does anyone know how to edit or append to an already existing systemd service inside of NixOS? also, if possible, I would like to only use the config file. you should probably also know I have no experience using flakes or the nix-env command.

any help would be appreciated, thank you.
MatsuNoKi (1 rep)
Apr 8, 2024, 02:59 AM • Last activity: Apr 8, 2024, 03:51 AM
1 votes
0 answers
397 views
UBUNTU - I am not asked for password after logging in with fingerprint
ubuntu password gnome-keyring fingerprint
I am running Ubuntu 22.04 with GNOME on a Dell XPS 13. I use the fingerprint as the main identification method, so I don't have to type the password each time I use `sudo`. The expected behavior is to log in using the fingerprint and then be asked for my password only once right after log in. My pro...
I am running Ubuntu 22.04 with GNOME on a Dell XPS 13.
I use the fingerprint as the main identification method, so I don't have to type the password each time I use sudo.
The expected behavior is to log in using the fingerprint and then be asked for my password only once right after log in. My problem is that more often than not I am not asked for the password after log in, so the keyring is not unlocked.
I have to log out and then log in again after waiting for fingerprint identification time out or using the wrong finger so I can enter the password and unlock the keyring. The behaviour is unpredictable. Is there a way to troubleshoot it or to unlock the keyring after login? EDIT Just to add more information, when I try to unlock the keyring using seahorse, the "unlock" button does not work.
Claudio (111 rep)
Mar 3, 2024, 07:02 PM • Last activity: Mar 17, 2024, 12:56 AM
1 votes
0 answers
83 views
How to backup and restore fprintd fingerprints?
backup fingerprint
I have configured `fprintd` on Arch Linux by following the [wiki](https://wiki.archlinux.org/title/fprint) and enrolled fingerprints with `fprintd-enroll`. According to this [question](https://unix.stackexchange.com/questions/644237/where-does-fprint-store-fingerprints) the fingerprints should be st...
I have configured fprintd on Arch Linux by following the [wiki](https://wiki.archlinux.org/title/fprint) and enrolled fingerprints with fprintd-enroll. According to this [question](https://unix.stackexchange.com/questions/644237/where-does-fprint-store-fingerprints) the fingerprints should be stored at /var/lib/fprint/ and /etc/fprintd.conf doesn't tell me anything. The only file in /var/lib/fprint/ is strongbad/synaptics/590ac910c956/7 with size 118 bytes and does not look like a fingerprint to me FP3^A^@^@^@synaptics^@590ac910c956^@^A^Gstrongbad^@^@FP1-20240227-7-2FA486E8-strongbad^@^@^@^?F^K^@^AFP1-20240227-7-2FA486E8-strongbad^> How do I backup and restore the fignerprints?
StrongBad (5491 rep)
Feb 28, 2024, 05:24 PM
0 votes
0 answers
1099 views
Kensington Desktop Fingerprint Key reader use with Ubuntu 23 / Linux Mint 21
ubuntu linux-mint drivers fingerprint
[This question][1] may have been posed some time ago. However, it appears there were no suitable solutions at the time ... So essentially, I would like to use a Kensington Desktop Fingerprint Key reader with Ubuntu 23 (or Linux Mint 21) for logging in and for general password entry via fingerprint d...
This question may have been posed some time ago. However, it appears there were no suitable solutions at the time ... So essentially, I would like to use a Kensington Desktop Fingerprint Key reader with Ubuntu 23 (or Linux Mint 21) for logging in and for general password entry via fingerprint detection, not unlike what may be done with Windows Hello, etc. So, I would like to know if anybody has found a solution for using this type of USB device (or perhaps another similarly priced device) for fingerprint login and password entry via fingerprint - one that works with the latest versions of Linux Ubuntu or Mint derivatives, etc. Otherwise, is this worth pursuing, or is it better to stick to Windows if one requires this functionality? Thanks, MM
citizen (101 rep)
Nov 28, 2023, 08:25 AM • Last activity: Nov 28, 2023, 10:46 AM
0 votes
0 answers
1098 views
How to authenticate with password in terminal, with fprintd authentication enabled?
debian pam authentication fingerprint
I enabled fingerprint authentication on my laptop running Debian 12 by following [this guide](https://forty.sh/posts/2021-02-19-enabling-fingerprint-authentication/): ``` $ doas apt install fprintd libpam-fprintd $ fprintd-enroll -f right-middle-finger $ fprintd-verify $ doas pam-auth-update --enabl...
I enabled fingerprint authentication on my laptop running Debian 12 by following [this guide](https://forty.sh/posts/2021-02-19-enabling-fingerprint-authentication/) : 
$ doas apt install fprintd libpam-fprintd
$ fprintd-enroll -f right-middle-finger
$ fprintd-verify
$ doas pam-auth-update --enable fprintd
Now every time I need to authenticate in the terminal, I use the fingerprint: 
username:~$ doas echo foo
Place your right middle finger on the fingerprint reader
foo
This is nice when I'm using my laptop undocked, when and I'm using external mouse and keyboard, I want to be able to authenticate with a password. I noticed that if I just wait, the fingerprint authentication just times out, and then I can successfully authenticate via password: 
username:~$ doas echo "foo"
Place your right middle finger on the fingerprint reader
Verification timed out
doas (username) password: 
foo
and same thing for failing the fingerprint authentication: 
username:~$ doas echo "foo"
Place your right middle finger on the fingerprint reader
Failed to match fingerprint
doas (username) password: 
foo
How can I get the same effect immediately and without reaching to the fingerprint sensor?
mkurz (227 rep)
Nov 12, 2023, 05:16 AM
1 votes
0 answers
393 views
How see fingerprints visually as images?
fingerprint
fprint stores fingerprints in /var/lib/fprint/, how can I view these visually as images? I can't find any docs of fprint, except a few short man pages.
fprint stores fingerprints in /var/lib/fprint/, how can I view these visually as images? I can't find any docs of fprint, except a few short man pages.
Virer (11 rep)
Oct 25, 2023, 11:36 PM
Showing page 1 of 20 total questions
Footer Ad - 728x90