Arch Linux User Repository

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.

Seems to be fixed with fprintd 1.90.8

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

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

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 :)

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

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

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

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
 }

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 :)

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