Package Details: libfprint-git 1:1.90.6.r3.g3560a0f-1

Git Clone URL: https://aur.archlinux.org/libfprint-git.git (read-only, click to copy)
Package Base: libfprint-git
Description: Library for fingerprint readers
Upstream URL: https://fprint.freedesktop.org/
Keywords: fprint
Licenses: LGPL
Conflicts: libfprint
Provides: libfprint, libfprint-2.so
Submitter: matthewbauer
Maintainer: timothy_gu
Last Packager: timothy_gu
Votes: 29
Popularity: 0.000001
First Submitted: 2009-09-01 02:39 (UTC)
Last Updated: 2020-12-16 21:14 (UTC)

Latest Comments

Strixpyrr commented on 2022-03-06 20:08 (UTC)

Yep, can confirm tests fail on elan and goodix:

6/23 libfprint:drivers / elanmoc           FAIL            1.16s   exit status 1
15/23 libfprint:drivers / goodixmoc         FAIL            1.20s   exit status 1

skan commented on 2021-10-20 02:41 (UTC)

Is anyone else getting build failures on elan and goodix drivers with current version?

kujou commented on 2020-12-03 13:15 (UTC)

I installed this package today, but it require another dependence:valgrind, which is not include in the PKGBUILD and have to install mannually.

timothy_gu commented on 2020-01-19 04:39 (UTC)

Alright, I've taken over the maintenance of this package. I use it fairly regularly for my ThinkPad T490s and will try to keep this up to date.

intelfx commented on 2020-01-18 14:38 (UTC)

@timothy_gu: Done. Thanks. I guess I'll just disown this package as I don't own/use compatible hardware anymore and don't have this installed...

timothy_gu commented on 2020-01-18 05:24 (UTC)

The latest version of libfprint requires some additional packages like libgusb. This works for me:

depends=('glib2>=2.56' 'libgusb>=0.3.0' nss pixman)
makedepends=(git gobject-introspection gtk-doc 'meson>=0.49.0')
checkdepends=('umockdev>=0.13.2')

With this you could also enable check() support:

check() {
  meson test -C build
}

Finally, the -D x11-examples=false in build() no longer does anything and can be removed. (Examples are all GTK-based now.)

intelfx commented on 2020-01-02 22:04 (UTC)

@ytexas @otaj Fixed. The official repo PKGBUILD strangely does not include gobject-introspection as a makedep.

ytexas commented on 2019-12-31 05:24 (UTC)

Need: gobject-introspection

Required by meson when compiling.

otaj commented on 2019-11-26 15:31 (UTC)

gobject-introspection is missing from makedepends

rindeal commented on 2018-09-25 23:07 (UTC)

I've developed a new driver for the proprietary binaries, which include support for VFS495 (among others). The source code and installation instructions are here - https://github.com/rindeal/libfprint-vfs_proprietary-driver.

SammysHP commented on 2018-08-14 09:41 (UTC)

@intelfx Yeah, this should be fine now, thanks! I'll delete/move my package libfprint-upstream-git.

intelfx commented on 2018-08-13 20:39 (UTC) (edited on 2018-08-13 20:39 (UTC) by intelfx)

@rocky7x I have since dropped the vfs495-daemon glue patch because it stopped applying and I have found no interest in forward-porting it again.

@SammysHP I believe now you have no concerns over this package?

rocky7x commented on 2018-08-13 13:55 (UTC)

Having VFS495 Validity device (138a:003f) and when I install this together with vfs495-daemon it doesn't work - throws No devices found - any idea? i added myself to plugdev and scanner groups...

nsood commented on 2018-06-06 15:53 (UTC) (edited on 2018-06-06 15:53 (UTC) by nsood)

For the time being, adding this line to prepare() in the PKGBUILD, before git apply, allows us to compile:

git checkout 3bf55a3e0766ca90f5befc1ed161b1c83005a962

Be warned though, this builds the last version of libfprint that did not migrate to Meson, and while it is relatively recent at the time of posting this comment, it might become outdated and unusable in time.

SammysHP commented on 2018-05-21 08:04 (UTC)

@intelfx

One and a half year later I want to ask you again if you can rename your package to something like "libfprint-validity-git" as it still contains a patch that is not and will not be included in upstream:

intelfx wrote:

Of course it won't be accepted by upstream at least due to license incompatibilities.

Meanwhile there are other packages which add custom patches, libfprint-vfs0090-git and libfprint-vfs0097-git.

charli9 commented on 2018-05-20 18:37 (UTC)

This package is broken since upstream changed to Meson instead of Autom4te

SammysHP commented on 2018-03-03 10:20 (UTC)

@thql

autom4te is included in the autoconf package which is included in the base-devel group. This group is a requirement for building packages from the AUR. Thus it is not necessary to include this dependency in the package.

thql commented on 2018-03-03 06:45 (UTC) (edited on 2018-03-03 06:47 (UTC) by thql)

There is a missing dependency in the package : autom4te

EDIT: or a typo, should it be automake instead?

intelfx commented on 2017-12-12 17:45 (UTC)

@oscar.h, @JUSHJUSH: look at the "Upstream URL" as indicated above. This is not a place to report bugs; I'm merely packaging libfprint.

JUSHJUSH commented on 2017-12-12 17:16 (UTC)

I have issue with VFS300 on Dell Vostro 3300 too. I can't get throught secound enroll.

oscar-h commented on 2017-06-18 12:28 (UTC)

Where can I report bugs with libfprint because with a VFS300 in a Dell Vostro 3500 (138a:0008) I can only get one pass when I run fprintd-enroll, and then nothing gets recognised

chris968 commented on 2017-01-24 23:06 (UTC)

I own a HP EliteBook 9470 with the following FingerPrint device : Bus 001 Device 003: ID 138a:003d Validity Sensors, Inc. VFS491 I make it work with libfprint-git AND vfs495-daemon !

bpietras commented on 2016-12-14 21:47 (UTC)

Firstly: Thank you. I tried the libprint-upstream-git first, without success. Secondly: Bus 001 Device 005: ID 138a:0007 Validity Sensors, Inc. VFS451 Fingerprint Reader Dec 14 21:46:36 bastard fprintd[23469]: now monitoring fd 15 Dec 14 21:46:36 bastard fprintd[23469]: device 0 claim status 0 Dec 14 21:46:36 bastard fprintd[23469]: start enrollment device 0 finger 7 Dec 14 21:46:36 bastard fprintd[23469]: enroll_stage_cb: result -19 Dec 14 21:46:36 bastard kernel: fprintd[23469]: segfault at 3d4 ip 00007fce8c152231 sp 00007ffd4297c930 error 4 in ld-2.24.so[7fce8c13d000+23000] Dec 14 21:46:36 bastard systemd[1]: Started Process Core Dump (PID 23474/UID 0). Dec 14 21:46:36 bastard systemd[1]: fprintd.service: Main process exited, code=dumped, status=11/SEGV Would the core be of use?

SammysHP commented on 2016-11-09 14:59 (UTC)

I created a package "libfprint-upstream-git" without additional patches. If you want just the code from upstream, please use that package.

intelfx commented on 2016-11-08 23:17 (UTC) (edited on 2016-11-08 23:18 (UTC) by intelfx)

Patch fixed, I've rearranged the definitions so hopefully that won't happen in the future. Of course it won't be accepted by upstream at least due to license incompatibilities. Why does that bother you so much (that you've even went as far as filing a formal orphan request)?

SammysHP commented on 2016-11-08 22:52 (UTC) (edited on 2016-11-08 23:05 (UTC) by SammysHP)

The patch won't apply anymore as upstream changed the code (phew, that wasn't expected). They added a driver for a Validity VFS0050 sensor. I'm not sure if there is a way to add compatibility with the devices in this patch. Anyway, I repeat my request to remove the patch and provide a clean upstream version of libfprint. You can create a separate package just for the patched version and send the patch upstream for review, of course. edit: Sorry, I just saw that the patch was already proposed and rejected. https://bugs.freedesktop.org/show_bug.cgi?id=97346

SammysHP commented on 2016-11-03 22:09 (UTC)

Then please rename this package so that I can upload a clean libfprint-git package.

intelfx commented on 2016-11-03 21:38 (UTC)

@SammysHP: The patch does not introduce new dependencies, and there is no official guideline forbidding such patches. Even if there was one, I would not maintain an extra patched package because I do not own such hardware. That said, I'll update the description to make this package easier to find.

SammysHP commented on 2016-11-03 21:17 (UTC) (edited on 2016-11-03 21:17 (UTC) by SammysHP)

Can you please move the patch to a separate package? libfprint-git should stay upstream.

intelfx commented on 2016-11-03 16:10 (UTC) (edited on 2016-11-03 16:10 (UTC) by intelfx)

@x11tete11x: yep, the patch had a redundant #include statement that referenced a package not in depends. Fixed, please try again.

x11tete11x commented on 2016-11-03 15:50 (UTC)

@intelfx looks like the last fixes, broke the package :O http://pastebin.com/Aq0BQim2

intelfx commented on 2016-11-03 13:43 (UTC)

@SammysHP, @parkerlreed, anyone: thanks for PKGBUILD and VFS495 patches and sorry for the latencies. Fixes applied, package updated.

SammysHP commented on 2016-11-03 11:28 (UTC) (edited on 2016-11-03 11:28 (UTC) by SammysHP)

Please replace "gdk-pixbuf2" dependency with "pixman" as written in the changelog: > 2015-02-03: v0.6.0 release > > […] > > * Library: > - Always use Pixman for image manipulation, gdk-pixbuf and ImageMagick > are not supported any more. Also the build() function is broken. autogen.sh does not replace configure. All options passed to autogen are useless. Here is a working PKGBUILD: https://gist.github.com/SammysHP/fad9909b4c7895b986ca40eacd522a17

parkerlreed commented on 2016-08-15 03:46 (UTC)

@skyeplus Thanks for the update. Sadly I don't have the laptop with that reader in it anymore but hope that helps some other people out there.

skyeplus commented on 2016-08-14 23:37 (UTC)

Hi, I adapted patch for latest lib version. libfprint interacts with vcsFPService through dynamic library via dlopen, so I guess it should gracefully fail if driver is not present. http://ix.io/1eh0

intelfx commented on 2016-05-10 14:42 (UTC)

@dreamingincode: sorry, totally missed your comment. Package is updated now.

dreamingincode commented on 2016-04-21 07:21 (UTC)

Please update pkgver in PKGBUILD, yaourt is notifying me of new update of this package every time, because 1:0.5.1.r13.g35e356f-1 is taken to be greater than 1:V.0.6.0.r32.g487dae0-1 (notice the "V"). Also per Arch Wiki (https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver.28.29_function): "maintainers should favor a pkgver that makes sense. To use pkgver(), you still need to declare the pkgver variable with the most recent value."

parkerlreed commented on 2016-03-25 21:21 (UTC) (edited on 2016-03-25 21:26 (UTC) by parkerlreed)

openssl098 currently has a pgp issue bypassed by --skipinteg I got a package created for the userspace driver. https://aur.archlinux.org/packages/vfs495-daemon/ Not sure how easily that patch could be updated. If you are able to port that to newer libfprint, I would be happy to help test it.

intelfx commented on 2016-03-25 17:59 (UTC)

@parkerlreed: As I have said, this patch utilizes a proprietary user-space daemon driver which is not packaged for Arch. If somebody packages it, then I will add the patch (provided that libfprint won't crash if the proprietary daemon is not available) and add the daemon to optdepends.

parkerlreed commented on 2016-03-25 14:34 (UTC) (edited on 2016-03-25 14:37 (UTC) by parkerlreed)

There is a patch for VFS495 against libfprint-0.0.6 https://balintbanyasz.wordpress.com/2015/03/27/get-validity-vfs-495-fingerprint-reader-working-in-ubuntu-14-04/ @hansmaulwurf, @yaxyo: These instructions work on Arch (Use rpmextract to extract the rpm files and place the files accordingly) but you lose out on being able to use fingerprint-gui since it has to be compiled against newer libfrpint. Here is the patch in particular http://ix.io/uXs (Patch does not apply at all on up to date libfrpint due to I assume massive code changes) EDIT: Also to run vcsFPService executable on boot I made a systemd unit file at /etc/systemd/system/fprint.service with the contents [Unit] Description=Fingerprint Service [Service] Type=forking ExecStart=/usr/bin/vcsFPService > /dev/null 2>&1 ExecStop=killall vcsFPService [Install] WantedBy=multi-user.target Then just systemctl daemon-reload, systemctl enable --now fprint.service

intelfx commented on 2016-03-25 11:43 (UTC) (edited on 2016-03-25 12:16 (UTC) by intelfx)

@hansmaulwurf, @yaxyo: there is no support for VFS495 in fprint, neither is there a fork which implements such support. The only way is to use a proprietary user-space daemon driver which is not packaged for arch, and I'm not willing to package it (e. g. because I do not have the necessary hardware to test it).

yaxyo commented on 2016-03-25 11:29 (UTC) (edited on 2016-03-25 11:29 (UTC) by yaxyo)

Hi, can you please include a patch for VFS495 Fingerprint Reader?

hansmaulwurf commented on 2015-11-30 22:33 (UTC)

Would it be possible to include a patch for VFS495? Like described here https://balintbanyasz.wordpress.com/2015/03/27/get-validity-vfs-495-fingerprint-reader-working-in-ubuntu-14-04/ ?

xantares commented on 2014-08-30 11:58 (UTC)

- no need to relaod ; udev rules are updated automatically except for already plugged devices: https://wiki.archlinux.org/index.php/udev - I added more rules for all supported devices from autosuspend rules - I update the message at install

xantares commented on 2014-08-21 11:43 (UTC)

I guess you can try: # udevadm control --reload-rules Maybe a more complete udev list is needed, could you check if your device is part of .rules file ?

hanckmann commented on 2014-08-21 09:31 (UTC)

After installing I get some advise from the installer. Among this advice is the following: [ALPM-SCRIPTLET] add uinput to the MODULES=() in /etc/rc.conf This is outdated as we are using systemd now. What should I do to load uinput? Also should this text be updated to the new situation.

xantares commented on 2014-08-10 16:05 (UTC)

Hi, That's the easy way, but the right way is to get that patch right for upstream inclusion. Sorry.

mwyraz commented on 2014-08-04 20:05 (UTC)

Hi, I have found a git-repo with a driver for Egistec S801U (lsusb: 1c7a:0801 LighTuning Technology Inc. Fingerprint Reader). The URL is https://github.com/lielfr/Libfprint-for-Egistec-S801U Recently that was ported to newer libfprint: https://bugs.freedesktop.org/show_bug.cgi?id=73762 Please have a look at this patches to see if you can somehow add it to the build. Kind regards, Michael.

garyvdm commented on 2013-07-26 10:56 (UTC)

Here is a updated pkgbuild: http://fpaste.org/28081/37483585/ It uses the new makepkg vsc features. Also made a number of options the same as extra/libfprint (autogen configure options, desc, etc.)

phragment commented on 2012-09-18 22:10 (UTC)

unless you need VFS300/VFS301 driver, consider using extra/libfprint

swiftgeek commented on 2012-07-14 21:20 (UTC)

It rly needs to move out from /lib :(

swiftgeek commented on 2012-05-18 17:21 (UTC)

/lib/udev/rules.d/60-fprint-autosuspend.rules causes errors in udev and is also redundant to laptop-mode-tools / pm-utils

phragment commented on 2012-01-24 00:27 (UTC)

@karol_007: fixed in pkgrel 4

karol_007 commented on 2012-01-16 10:49 (UTC)

I get mv: cannot stat `/home/karol/apps/libfprint-git/pkg/etc/udev/rules.d/*': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... There's no "$pkgdir"/etc/ so it fails.

commented on 2011-02-28 21:12 (UTC)

'libusb1' is not a package available somewhere. Building worked for me after I changed it to 'libusb'.

andrew9888 commented on 2010-05-09 11:40 (UTC)

I compiled this against libusb1 from extra and it works fine. There's no need to depend on libusb-beta anymore.