[Fingerforce-devel] Bug#979143: fprintd logs "failed to claim device" and refused to start (nor does fprintd-verify work)
Markus Wolf
knister.peter at shadowrun-clan.de
Sun Jan 3 14:18:49 GMT 2021
Package: fprintd
Version: 1.90.8-1
Severity: normal
X-Debbugs-Cc: knister.peter at shadowrun-clan.de
Dear Maintainer,
I've installed fprintd to get my fingerprint reader (06cb:00bd Synaptics, Inc. Prometheus MIS Touch Fingerprint Reader) working.
This worked as expected from the first tries. I've enrolled by fingerprints and tried with fprintd-verify.
Also a screenlock did work as expected.
I've noticed that after a suspend the fprintd didn't work any longer (also not from a lockscreen with GDM).
I've tried to debug this as far as I can, but the only thing I've found out are my journald logs or the fprintd-verify error output:
xxx at xxx:~$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
failed to claim device: GDBus.Error:net.reactivated.Fprint.Error.AlreadyInUse: Device was already claimed
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-5-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fprintd depends on:
ii dbus 1.12.20-1
ii libc6 2.31-6
ii libfprint-2-2 1:1.90.5-2
ii libglib2.0-0 2.66.4-1
ii libpolkit-gobject-1-0 0.105-29
ii policykit-1 0.105-29
fprintd recommends no packages.
fprintd suggests no packages.
-- no debconf information
More information about the Fingerforce-devel
mailing list