Package Details: libfprint-vfs009x-git 1:1.90.1.r6.g2978dc0-2

Git Clone URL: https://aur.archlinux.org/libfprint-vfs009x-git.git (read-only, click to copy)
Package Base: libfprint-vfs009x-git
Description: Library for fingerprint readers (includes libre vfs0090 and vfs0097 driver)
Upstream URL: https://github.com/3v1n0/libfprint
Licenses: LGPL
Conflicts: fprintd, libfprint
Provides: libfprint, libfprint-2.so, libfprint-vfs0090, libfprint-vfs0097, libfprint-vfs009x
Replaces: libfprint, libfprint-vfs0090, libfprint-vfs0097, libfprint-vfs009x
Submitter: Depau
Maintainer: None
Last Packager: Stebalien
Votes: 13
Popularity: 0.022214
First Submitted: 2020-06-21 21:32 (UTC)
Last Updated: 2021-07-01 23:18 (UTC)

Pinned Comments

Depau commented on 2020-07-25 16:17 (UTC) (edited on 2020-10-09 19:21 (UTC) by Depau)

vfs0097 users

The package will automatically apply a patch required for the vfs0097 reader if one is found in the system at build time, it will otherwise build for vfs0090. You can force a preferred behavior by exporting VFS0097=1 or =0.

If you have any issues, make sure talk about it https://gitter.im/Validity90/Lobby so it has a chance to get fixed.

GH issues have also been enabled by upstream, so make sure you check that as well: https://github.com/3v1n0/libfprint/

vfs0090 users

The driver should work as expected, but same as above for any issues.

Latest Comments

Stebalien commented on 2022-06-29 04:26 (UTC)

Unfortunately, I no longer use nor can I maintain this package anymore.

K4LCIFER commented on 2022-06-29 01:28 (UTC)

Can't build due to errors:

libfprint/meson.build:1:0: ERROR: Unknown options: "x11-examples"

A full log can be found at /home/<username>/.cache/yay/libfprint-vfs009x-git/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: libfprint-vfs009x-git

MartinX3 commented on 2022-02-03 14:22 (UTC)

@kugelblitz It doesn't conflict with fprintd. Newer versions are not compatible.

kugelblitz commented on 2022-02-03 10:24 (UTC)

Is there any reason for the package to be conflicting with fprintd?

ragusa87 commented on 2022-01-30 21:38 (UTC) (edited on 2022-01-30 21:40 (UTC) by ragusa87)

This packages conflicts with fprintd>=1.92.0, so I had to downgrade fprintd to version 1.90.1-1 to make my fingerprint reader (138a:0090) work. I also had to remove the x11-examples option as mentioned in previous comments to be able to build this package.

pacman -Q | grep fprint
fprintd 1.90.1-1
libfprint-vfs009x-git 1:1.90.1.r6.g2978dc0-2

realh commented on 2021-12-29 13:34 (UTC)

@hfd4220287: The x11-examples option seems to have been removed. It looks like it's been replaced by "gtk-examples". I edited that in PKGBUILD and it built successfully.

hfd4220287 commented on 2021-12-27 07:17 (UTC) (edited on 2021-12-27 07:43 (UTC) by hfd4220287)

In my computer also happened this error:

A full log can be found at /home/eastoo/.cache/yay/libfprint-vfs009x-git/src/build/meson-logs/meson-log.txt
==> ERROR: A failure occurred in build().
    Aborting...
-> error making: libfprint-vfs009x-git

Follow line is the full log in /home/xxxx/.cache/yay/libfprint-vfs009x-git/src/build/meson-logs/meson-log.txt:

Build started at 2021-12-27T14:51:22.846023
Main binary: /usr/bin/python
Build Options: -Db_lto=true -Db_pie=true -Dx11-examples=false -Ddoc=false -Dudev_rules_dir=/usr/lib/udev/rules.d -Dprefix=/usr -Dlibexecdir=lib -Dsbindir=bin -Dauto_features=enabled -Dbuildtype=plain -Dwrap_mode=nodownload
Python system: Linuxvim k
The Meson build system
Version: 0.60.3
Source dir: /home/eastoo/.cache/yay/libfprint-vfs009x-git/src/libfprint
Build dir: /home/eastoo/.cache/yay/libfprint-vfs009x-git/src/build
Build type: native build
libfprint/meson.build:1:0: ERROR: Unknown options: "x11-examples"

Follow line is my computer information:

1. System: EndeavourOS + KDE
2. Hardware: Thinkpad X1 carbon 2016

Please help me with these problem, thanks very much!

classicalover commented on 2021-12-14 20:30 (UTC) (edited on 2021-12-19 04:00 (UTC) by classicalover)

Hello, I also ran into the same issue by vladimir1922 with the error "Unknown options: "x11-examples". I had to edit the PKGBUILD during install (for yay, I used yay --editmenu -S libfprint-vfs009x-git) on line 70 and remove "-D x11-examples=false" in order for the package to compile successfully. Perhaps this needs to be fixed and re-committed @Depau @Stebalien? I apologize for the amateur comment, I am a new Arch user.

vladimir1922 commented on 2021-12-14 18:13 (UTC)

Compilation fails for me:

libfprint/meson.build:1:0: ERROR: Unknown options: "x11-examples"

MartinX3 commented on 2021-07-02 10:05 (UTC)

Thank you for your work. It's sad to hear. :(

Stebalien commented on 2021-07-01 23:18 (UTC)

@MartinX3 Done. I also tried rebasing upstream but it looks like there's been a complete refactor. I'm not sure when this will be fixed, if ever.

MartinX3 commented on 2021-07-01 23:03 (UTC) (edited on 2021-07-01 23:05 (UTC) by MartinX3)

Broken since fprintd 1.92.0

/usr/lib/fprintd: symbol lookup error: /usr/lib/fprintd: undefined symbol: fp_device_has_feature, version LIBFPRINT_2.0.0

Please force fprintd < 1.92.0 until this project got updated.

MartinX3 commented on 2020-12-12 12:03 (UTC)

Seems to be fixed with fprintd 1.90.8

Stebalien commented on 2020-12-10 17:50 (UTC)

@MartinX3 Yes. It appears to "work", but it seems to crash/close a few times before it finally does.

MartinX3 commented on 2020-12-10 12:16 (UTC)

Does someone else get issues since arch updated the fprint package to 1.90.6 ?

Depau commented on 2020-12-06 22:38 (UTC)

Hey guys, my ThinkPad with the VFS0090 fingerprint reader just died on me.

I can't test the changes any more so I will be disowning it.

Take care of it :)

j.r commented on 2020-12-06 19:32 (UTC)

For anyone having the same problem as me, the following patch could be applied to the build metadata to get it working with latest upstream changes: https://paste.sr.ht/~j-r/761b4178c643d8bd03bada73c4da01de2943f020

j.r commented on 2020-11-30 17:14 (UTC)

0001-Do-not-checkout-the-vfs0090-submodule-in-the-meson-s.patch would not apply anymore because upstream also added changes at this point

Depau commented on 2020-10-27 23:48 (UTC)

dlainhart: Thanks for the suggestions, looks good to me. Package updated.

dlainhart commented on 2020-10-26 11:43 (UTC)

Howdy, I tried building this package in a chroot and I found a few problems in the PKGBUILD.

First off: it's missing 'libgusb' in depends. It's a hard dependency in meson.build so it ought to be in the PKGBUILD.

Second: Cairo is only required for the test suite, so it should be in checkdepends instead of depends. Quoting meson.build: # The following dependencies are only used for tests cairo_dep = dependency('cairo', required: false)

Third: Building in a chroot will cause meson to puke out with the following error message: Run-time dependency udev found: NO (tried pkgconfig)

libfprint/meson.build:208:8: ERROR: Dependency "udev" not found, tried pkgconfig Inspecting meson.build revealed that it's calling pkgconfig to look for the udevdir variable; this comes from /usr/share/pkgconfig/udev.pc: $ pkg-config --path --variable=udevdir udev /usr/share/pkgconfig/udev.pc /usr/lib/udev $ pacman -Qo /usr/share/pkgconfig/udev.pc /usr/share/pkgconfig/udev.pc is owned by systemd 246.6-1 Adding systemd to makedepends does indeed fix the build. Examining meson.build again shows that adding systemd as a makedepends can be avoided with meson configure -D udev_rules_dir=/usr/lib/udev/rules.d: if get_option('udev_rules') udev_rules_dir = get_option('udev_rules_dir')

    if udev_rules_dir == 'auto'
        udev_dep = dependency('udev')
        udev_rules_dir = udev_dep.get_pkgconfig_variable('udevdir') + '/rules.d'
    endif
endif

I prepared a patch to fix these issues: --- PKGBUILD.old 2021-10-26 07:38:20.879362789 -0400 +++ PKGBUILD 2020-10-26 07:38:08.535964485 -0400 @@ -9,8 +9,9 @@ arch=(i686 x86_64) url="https://github.com/3v1n0/libfprint" license=(LGPL) -depends=(libusb nss pixman gnutls openssl gobject-introspection glib2 cairo pixman nss openssl) +depends=(libusb nss pixman gnutls openssl gobject-introspection glib2 libgusb) makedepends=(git meson gtk-doc pkgconf usbutils) +checkdepends=(cairo) optdepends=( "fprintd: D-Bus daemon that manages fingerprint readers" "validity-sensors-tools: Flash, factory reset and pair Validity fingerprint sensors 009x" @@ -66,7 +67,7 @@

 build() {
   cd "$srcdir"
-  arch-meson $_pkgname build -D x11-examples=false -D doc=false
+  arch-meson $_pkgname build -D x11-examples=false -D doc=false -D udev_rules_dir=/usr/lib/udev/rules.d
   ninja -C build
 }

Depau commented on 2020-10-19 23:13 (UTC)

Oops, embarassing mistake. I indeed intended to use -N/--forward.

We should do a contest for the package with the highest pkgrel in the AUR, I'd win it :)

Stebalien commented on 2020-10-19 16:57 (UTC)

Ok, one more fix that I missed. You need patch -Np1, not patch -np1. -n means the patch is a "normal" (not "unified") diff.

Depau commented on 2020-10-19 13:35 (UTC)

@Stebalien patched, thank you.

Stebalien commented on 2020-10-15 17:26 (UTC)

So, it looks like the patch won't work if applied before the arch-meson ... line as that one will re-checkout the submodules (erasing the patch). I'm currently running the arch-meson command in the prepare function, but the alternative is to run it in build.

Depau commented on 2020-10-11 00:38 (UTC)

Thank you all for your feedback, all the reported issues should now be fixed.

Thanks @Stebalien for the patch.

tledford commented on 2020-10-10 21:24 (UTC)

Attempt to build via pamac on Manjaro Gnome yields:

|index f3c2072..e8b4619 100644 |--- a/vfs0090.h |+++ b/vfs0090.h


File to patch: Skip this patch? [y] Skipping patch. 2 out of 2 hunks ignored ==> ERROR: A failure occurred in prepare(). Aborting...

Stebalien commented on 2020-10-10 19:02 (UTC)

Patch to fix the PKGBUILD: https://gist.github.com/5e6f91229968f92eaf85a0c971d1dc0c

  1. Uses warning instead of messing around with color codes manually.
  2. Checks out the appropriate submodules so the build works.

MartinX3 commented on 2020-10-10 09:19 (UTC)

Sadly the neweest package change broke the aur package with the following error message

libfprint-vfs009x-git/PKGBUILD: line 36: local: RED: Readonly variable.

Depau commented on 2020-10-09 19:17 (UTC) (edited on 2020-10-09 19:29 (UTC) by Depau)

Alright guys, I updated the package and added some checks:

  • export VFS0097=1 or =0 will respectively force the VFS0097 patch on or off.
  • Unless explicitly forced, the PKGBUILD tries to see if a VFS0097 reader is attached to the system, and if it is, it applies the patch.

Please let me know if it works :)

EDIT: I also noticed 3v1n0 created a new repo on XDG's GitLab, I asked which one should be used and I'll update the package accordingly. https://gitlab.freedesktop.org/3v1n0/libfprint/-/issues/3

Depau commented on 2020-10-09 18:58 (UTC)

Thanks @ectospasm for linking this. I'm aware that 3v1n0 is quite busy so he doesn't look at GitHub issues very often.

This is the actual patch: https://github.com/piotrekzurek/libfprint-tod-vfs0090/commit/804bdcfe4179a2f350af5344dc0362111ab017ae

I just tested it on my laptop (vfs0090) and it does NOT work with the patch.

However, as a temporary workaround I can make it so that the patch is applied if you export VFS0097=1 at build-time.

The issue ultimately needs to be addressed by upstream.

ectospasm commented on 2020-10-07 22:22 (UTC) (edited on 2020-10-07 22:31 (UTC) by ectospasm)

Anyone experiencing a protocol error with vfs0097 should review this upstream issue. There's a patch to getting it working, but I had to use a third-party GitHub repository to get it.

Depau commented on 2020-07-25 16:17 (UTC) (edited on 2020-10-09 19:21 (UTC) by Depau)

vfs0097 users

The package will automatically apply a patch required for the vfs0097 reader if one is found in the system at build time, it will otherwise build for vfs0090. You can force a preferred behavior by exporting VFS0097=1 or =0.

If you have any issues, make sure talk about it https://gitter.im/Validity90/Lobby so it has a chance to get fixed.

GH issues have also been enabled by upstream, so make sure you check that as well: https://github.com/3v1n0/libfprint/

vfs0090 users

The driver should work as expected, but same as above for any issues.

Depau commented on 2020-07-20 15:43 (UTC) (edited on 2020-07-20 15:44 (UTC) by Depau)

You should probably ask in the Gitter chat: https://gitter.im/Validity90/Lobby

As a temporary workaround you can use downgrader from AUR to download fprintd v0.90 and install this package, then add it to IgnorePkg so it doesn't get upgraded.

RainbowNia commented on 2020-07-20 06:58 (UTC)

Okay. I have installed this other one but when I run fprintd-enroll <username> I get failed to claim device: Open failed with error: The driver encountered a protocol error with the device. Do you know any fix?

Depau commented on 2020-07-19 15:27 (UTC)

Oh, I just realized you're commenting on libfprint-vfs0097-git. This package is out of date, libfprint-vfs009x-git should replace it.

Depau commented on 2020-07-19 15:25 (UTC)

I think you're mixing up something. libfprint-2.so is provided by this AUR package.

Just install this AUR package and then fprintd from the repos. You're probably seeing errors because most AUR helpers will install repo packages first and then AUR packages, while this package needs to be installed first otherwise fprintd will also want to pull libfprint from the repo.

$ pacman -Qi fprintd
Name            : fprintd
Version         : 1.90.1-1
Description     : D-Bus service to access fingerprint readers
Architecture    : x86_64
URL             : https://www.freedesktop.org/wiki/Software/fprint/fprintd
Licenses        : GPL
Groups          : fprint
Provides        : None
Depends On      : glib2  libfprint  polkit  dbus  dbus-glib  libsystemd  libfprint-2.so=2-64
Optional Deps   : None
Required By     : None
Optional For    : gdm  libfprint-vfs009x-git
Conflicts With  : None
Replaces        : None
Installed Size  : 520.49 KiB
Packager        : Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Build Date      : Thu 27 Feb 2020 07:28:45 PM CET
Install Date    : Tue 23 Jun 2020 08:05:19 PM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature
$ pacman -Qi libfprint-vfs009x-git
Name            : libfprint-vfs009x-git
Version         : 1:1.90.1.r0.g82aed23-1
Description     : Library for fingerprint readers (includes libre vfs0090 and vfs0097 driver)
Architecture    : x86_64
URL             : https://github.com/3v1n0/libfprint
Licenses        : LGPL
Groups          : fprint-git
Provides        : libfprint  libfprint-2.so=2-64  libfprint-vfs009x  libfprint-vfs0090  libfprint-vfs0097
Depends On      : libusb  nss  pixman  gnutls  openssl
Optional Deps   : fprintd: D-Bus daemon that manages fingerprint readers [installed]
                  validity-sensors-tools: Flash, factory reset and pair Validity fingerprint sensors 009x
Required By     : fprintd
Optional For    : None
Conflicts With  : libfprint
Replaces        : libfprint  libfprint-vfs009x  libfprint-vfs0090  libfprint-vfs0097
Installed Size  : 765.58 KiB
Packager        : Unknown Packager
Build Date      : Sun 19 Jul 2020 05:22:56 PM CEST
Install Date    : Sun 19 Jul 2020 05:23:34 PM CEST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : None

RainbowNia commented on 2020-07-18 07:08 (UTC)

But that causes a compatibility error because this does not include libfprint-2.so Does that mean we cannot use this tool?

Depau commented on 2020-07-18 01:47 (UTC)

The latest

RainbowNia commented on 2020-07-17 10:35 (UTC)

Which version of fprintd do we need?

n3hima commented on 2020-07-12 04:13 (UTC)

Hi, please can the gobject-introspection package be added to the build dependencies

gugah commented on 2020-06-20 16:03 (UTC)

@Depau could you check pkgver on the PKGBUILD?, yay keeps trying to update the package: aur/libfprint-vfs0090-git 1:v1.90.1+vfs009x.1.r0.g82aed23-1 -> 1:1.90.r0.gb8e684e-1

Depau commented on 2020-06-16 02:21 (UTC)

Package has been updated and it should work with updated fprintd. If you added fprintd to IgnorePkg you can now remove it and update both this package and fprintd.

You need to perform the enrolling again.

I think this should also work with vfs0097 but I'm not sure, I asked Marco for confirmation.

I also packaged validity-sensors-tools in case you need to perform initialization and you don't wanna use snap. Note that, in case you're concerned, upstream didn't specify a license; also it uses stuff from the proprietary drivers from the Lenovo websites, I haven't looked around too much.

Depau commented on 2020-06-15 23:41 (UTC)

I'm sure happy to update, hurray!

Sorry for the delay :/

Hork commented on 2020-06-13 03:59 (UTC)

Upstream updated. Would you like to update this package?

Depau commented on 2020-04-12 00:40 (UTC) (edited on 2020-06-16 00:05 (UTC) by Depau)

EDIT 2020-06-16:

Upstream rebased on libfprint master, package has been updated.


Package is still broken, you still need to get an older fprintd version < 1.90 from ALA.

You can do that with downgrader.

Depau commented on 2020-02-28 13:54 (UTC)

In case anybody was wondering, Arch updated fprintd to the latest version, which requires libfprint-2.so, which is not provided by this package.

Until upstream merges libfprint >= 1.90 into his fork (which I tried to do myself on the vfs0090 fork but it requires manual API usage fixing, no time for that - sorry), you'll have to stick with an older version of fprintd.

Depau commented on 2020-02-28 00:18 (UTC)

In case anybody was wondering, the build now works. However, Arch updated fprintd to the latest version, which requires libfprint-2.so, which is not provided by this package.

Until upstream merges libfprint >= 1.90 into his fork (which I tried to do myself but it requires manual API usage fixing, no time for that - sorry), you'll have to stick with an older version of fprintd.

Depau commented on 2020-01-03 22:06 (UTC) (edited on 2020-01-03 22:23 (UTC) by Depau)

@hmu confirmed. That's an upstream issue, however. I'll report that and consider adding a patch to the package.

EDIT: Unless I'm missing something, it looks like 3v1n0 rebased his repo on top of upstream master, but they made changes to the API and it needs refactoring. So, removing the #include "driver_ids.h" line doesn't help.

Long story short, the package is broken and there's not much I can do about it. Please help upstream and send pull requests if you can :)

hmu commented on 2019-12-27 22:37 (UTC)

This doesn't build for me, it complains about driver_ids.h missing. Apparently not all references where removed in the drivers.

Depau commented on 2019-01-24 15:42 (UTC)

@djres Reboot. In general, ask upstream.

djres commented on 2019-01-23 12:26 (UTC)

I'm getting some error:

$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error -5

Anyone knows what's wrong?

Depau commented on 2019-01-15 21:00 (UTC)

Sorry for having you waiting, I updated the PKGBUILD.

It stopped building because upstream switched the build system from GNU autotools to Meson.

djres commented on 2019-01-15 14:26 (UTC)

I get the same error as @speculees

speculees commented on 2019-01-11 13:19 (UTC)

Can't install this package. Getting error:

.../.cache/yay/libfprint-vfs0090-git/PKGBUILD: line 34: ./autogen.sh: No such file or directory

Depau commented on 2018-05-15 11:59 (UTC)

hrenod's package uses another repo to support 0097. This one is tested with 0090.

meijin commented on 2018-05-14 19:51 (UTC)

please use hrenod source which is actually wrking with 0097 device

meijin commented on 2018-05-10 07:12 (UTC)

Is there any instractures how to actually use this package?