Package Details: fprintd-vfs_proprietary 0.8.1-2

Git Clone URL: https://aur.archlinux.org/fprintd-vfs_proprietary.git (read-only, click to copy)
Package Base: fprintd-vfs_proprietary
Description: D-Bus service to access fingerprint readers, modified for the vfs_proprietary plugin
Upstream URL: https://www.freedesktop.org/wiki/Software/fprint/fprintd
Licenses: GPL
Groups: fprint
Conflicts: fprintd
Submitter: XAVeRY
Maintainer: kapcom01
Last Packager: kapcom01
Votes: 5
Popularity: 0.000000
First Submitted: 2019-01-27 16:41 (UTC)
Last Updated: 2020-06-28 18:05 (UTC)

Latest Comments

1 2 3 Next › Last »

kapcom01 commented on 2020-07-08 11:34 (UTC) (edited on 2020-07-10 22:55 (UTC) by kapcom01)

@FalsePerspective the packages fprintd-vfs_proprietary and libfprint-vfs_proprietary-git do not support your device. You should install libfprint and fprintd packages which are on the official Arch Repositories

FalsePerspective commented on 2020-07-08 10:54 (UTC) (edited on 2020-07-08 10:58 (UTC) by FalsePerspective)

According to the documentation, my fingerprint reader is supported by libfprint

[  637.060251] usb 1-1: New USB device found, idVendor=04f3, idProduct=0c26, bcdDevice= 1.40
[  637.060258] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  637.060262] usb 1-1: Product: ELAN:Fingerprint

However, after I start the service, it can't find my device:

$ fprintd-enroll
list_devices failed: No devices available

kermitaln commented on 2020-06-29 07:21 (UTC)

Thanks @kapcom01. We are at the same point.

I need to restart frintd daemon, wait ~40s and then use fprintd-{whatever}. I am able to enroll, but not to verify:

Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
 - #0: right-index-finger
Verify result: verify-no-match (done)

Keep debugging...

kapcom01 commented on 2020-06-28 21:21 (UTC) (edited on 2020-06-28 21:37 (UTC) by kapcom01)

@kermitaln: run sudo systemctl restart fprintd.service, watch sudo journalctl -f -u fprintd and wait for systemd[1]: fprintd.service: Succeeded. to appear (about 40 seconds later)

Then you may be able to run (without timeouts) fprintd-enroll and another 40 seconds later fprintd-verify. For me this worked but I get Verify result: verify-no-match (done) every time I try to verify any fingerprint.. Something is wrong..

kermitaln commented on 2020-06-28 21:04 (UTC)

Same behavior, yes.

Each call to fprintd-{whatever} prints:

systemd[1]: Starting Fingerprint Authentication Daemon...
systemd[1]: Started Fingerprint Authentication Daemon.
(and after a while...)
systemd[1]: fprintd.service: Succeeded.

I also get timeouts when enrolling:

❯ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
EnrollStart failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
systemd[1]: Starting Fingerprint Authentication Daemon...
systemd[1]: Started Fingerprint Authentication Daemon.
fprintd[40718]: Timed out waiting for capture-helper
fprintd[40718]: capture-helper output:
                syslog: Validity_vfs_dev_init: Entry
                syslog: Validity_vfs_dev_init: Exit
                SIGALRM caught: Timed out waiting for capture

                Sensor usb#vid_138a#pid_003f#00a0fe347780 plugged.

                Waiting for finger swipe ...
fprintd[40718]: activation failed with error -110
fprintd[40718]: failed to start enrollment
systemd[1]: fprintd.service: Succeeded.

kapcom01 commented on 2020-06-28 15:20 (UTC) (edited on 2020-06-28 21:32 (UTC) by kapcom01)

EDIT: I uploaded a workaround and now you can successfully install the package.

But for me this was not enough.. Maybe you have better luck on your system.

Unfortunately the best result I could get was to enroll my fingers but without the ability to verify them.

EDIT2: commands fprintd-enroll and fprintd-verify must be run 40 seconds apart from each other.. for some reason..

kermitaln commented on 2020-06-28 12:51 (UTC) (edited on 2020-06-28 12:52 (UTC) by kermitaln)

Same problem. I've tried to compile fprintd following PKGBUILD steps:

/usr/bin/ld: ./.libs/libfprintd.a(device.o):/tmp/fprintd/src/storage.h:47: multiple definition of `store'; main.o:/tmp/fprintd/src/storage.h:47: first defined here
collect2: error: ld returned 1 exit status

Any workaround?

paccio84 commented on 2020-06-19 14:23 (UTC)

I have the same problem:

make: *** [Makefile:448: check-recursive] Error 1 ==> ERROR: A failure occurred in build(). Aborting...

kapcom01 commented on 2020-06-18 12:33 (UTC) (edited on 2020-06-28 18:40 (UTC) by kapcom01)

same problem here.

  CCLD     fprintd
/usr/bin/ld: ./.libs/libfprintd.a(device.o):(.bss+0x0): multiple definition of `store'; main.o:(.bss+0x0): first defined here
collect2: error: ld returned 1 exit status