You are not logged in.
My fingerprint reader (04f3:0c6e) is listed as supported but when I try to enroll my fingerprint, it bails out with the "enroll disconnected" error on both terminal and KDE settings.
While fiddling a bit with fprintd-verify, I see this message:
~ » fprintd-verify
Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.AlreadyInUse: Device was already claimedI searched for this message in the forum and tried the following script, as I was using fingerprint unlock in Windows before:
Nvm got it to work. I just ran this python script https://gitlab.freedesktop.org/libfprin … te_1063158 and enrolled my fingerprint again and that solved it.
But the output claims it's somehow "already in use":
libusb: warning [libusb_exit] device 1.2 still referenced
libusb: warning [libusb_exit] device 1.1 still referenced
libusb: warning [libusb_exit] application left some devices open
<__gi__.FpiDeviceElan object at 0x7fd5dde05a00 (FpiDeviceElan at 0x55d0278db3f0)>
elan
0
Traceback (most recent call last):
File "<python-input-2>", line 12, in <module>
dev.open_sync()
~~~~~~~~~~~~~^^
gi.repository.GLib.GError: g-usb-device-error-quark: USB error on device 04f3:0c6e : Resource busy [-6] (10)Just in case: I dualboot Windows 11 and I've already "disabled" fingerprint unlock on it, but still no luck.
I previously disabled Windows Fast boot both in the BIOS and in Windows itself, but still no luck anyway.
Is there any workaround/fix or am I missing something? Thank you in advance.
Offline
echo 1 > /sys/devices/user_of_fingerprint/detach
its up to you to determine who is use that device already.
issue verbose lsusb, lspci (eg lsusb -vv, lspci -vv)
Offline
echo 1 | LANG=C sudo tee /sys/devices/user_of_fingerprint/detach
tee: /sys/devices/user_of_fingerprint/detach: No such file or directory
1Maybe something I'm missing out here?
Offline
"user_of_fingerprint" is a placeholder; a hint for you.
You have to determine EXACT path if there is any.
its the name of kernelmodule/driver that claims that device.
issue the commands as 'root' btw.
Offline
"You have to determine EXACT path if there is any.
its the name of kernelmodule/driver that claims that device.
~ » sudo find /sys/devices/ -name '*detach*'
[sudo] contraseña para lito:
/sys/devices/virtual/sound/ctl-led/speaker/card1/detach
/sys/devices/virtual/sound/ctl-led/speaker/card0/detach
/sys/devices/virtual/sound/ctl-led/mic/card1/detach
/sys/devices/virtual/sound/ctl-led/mic/card0/detachSeems to be nothing fingerprint-related in there...
Offline
seems no module claims device. Then a userspace process/service is make you trouble.
'fuser /to/fingerprint/device' command give you some hint. my example path is palaceholder.
Offline
sudo fuser /dev/input/event* you mean this? I googled and couldn't find exact info about the fingerprint dev location
Offline
try them:
dmesg | grep -i elan
dmesg | grep -i input
dmesg | grep -i event
sudo grep -irl elan /sys/devices
sudo grep -irl finger /sys/devices
to print all open fds:
sudo lsof
to show pid of processes that opens a device:
sudo fuser -m /dev/null
if you determine process kill it. disable it service or configure to not messing with fingerprint device.
edit: libinput suspected.
Last edited by unixman (2025-07-03 18:50:34)
Offline
Now both the script and fprintd-verify fail with a different error, so I think there's no more "resource busy" for now:
script:
<__gi__.FpiDeviceElan object at 0x7f9093596500 (FpiDeviceElan at 0x55b7beb8ed10)>
elan
0
Traceback (most recent call last):
File "<python-input-0>", line 16, in <module>
prints = dev.list_prints_sync()
gi.repository.GLib.GError: fp - device - error - quark: Device has no storage (1)fprintd-verify:
~ » fprintd-verify
Using device /net/reactivated/Fprint/Device/0
ListEnrolledFingers failed: GDBus.Error:net.reactivated.Fprint.Error.NoEnrolledPrints: Failed to discover printsdmesg | grep -i elan
dmesg | grep -i input
dmesg | grep -i event
sudo grep -irl elan /sys/devices
sudo grep -irl finger /sys/devices
Offline