3v1n0/libfprint

No Devices Available on Ubuntu 20.10

neoromantique opened this issue · 2 comments

Hi! I have installed python-validity as a snap, and did everything as per instructions, but I keep getting

list_devices failed: No devices available

from fprintd. I am running t470s with 138a:0097

Hi, I am seeing the same. Here some context:

$ snap list validity-sensors-tools
Name                    Version            Rev  Tracking       Publisher  Notes
validity-sensors-tools  0.5+git23.5813f6e  65   latest/stable  3v1n0      -
$ apt-cache policy libfprint-2-2 libfprint-2-tod-vfs0090 libfprint-2-tod1 fprintd
libfprint-2-2:
  Installed: 1:1.90.3+tod1-0ubuntu1
  Candidate: 1:1.90.3+tod1-0ubuntu1
  Version table:
 *** 1:1.90.3+tod1-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
libfprint-2-tod-vfs0090:
  Installed: 0.90~f2
  Candidate: 0.90~f2
  Version table:
 *** 0.90~f2 500
        500 http://ppa.launchpad.net/3v1n0/libfprint-vfs0090/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
libfprint-2-tod1:
  Installed: 1:1.90.3+tod1-0ubuntu1
  Candidate: 1:1.90.3+tod1-0ubuntu1
  Version table:
 *** 1:1.90.3+tod1-0ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
fprintd:
  Installed: 1.90.1-1ubuntu1
  Candidate: 1.90.1-1ubuntu1
  Version table:
 *** 1.90.1-1ubuntu1 500
        500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
        100 /var/lib/dpkg/status
$ lsusb | fgrep Validity
Bus 001 Device 012: ID 138a:0097 Validity Sensors, Inc.
$ sudo validity-sensors-tools --tool led-dance
# works
$ sudo validity-sensors-tools.enroll --finger-id 0
# also works
$ fprintd-verify
list_devices failed: No devices available
$ sudo systemctl status fprintd
● fprintd.service - Fingerprint Authentication Daemon
     Loaded: loaded (/lib/systemd/system/fprintd.service; static)
     Active: inactive (dead)
       Docs: man:fprintd(1)

Oct 25 02:53:33 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:53:45 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:53:45 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:54:15 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:58:19 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:58:19 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:58:49 x1-yoga systemd[1]: fprintd.service: Succeeded.
Oct 25 02:12:40 x1-yoga systemd[1]: Starting Fingerprint Authentication Daemon...
Oct 25 02:12:40 x1-yoga systemd[1]: Started Fingerprint Authentication Daemon.
Oct 25 02:13:10 x1-yoga systemd[1]: fprintd.service: Succeeded.

What can be done to debug this further?

osbre commented

I compiled this project manually on Fedora, and I get the same error:

> fprintd-enroll
Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available