Arch Linux User Repository

If you're installing this as a dependency of libfprint-vfs_proprietary-git, please keep in mind that you also need to replace the standard fprintd with fprintd-vfs_proprietary .

If you're installing this as a dependency of libfprint-vfs_proprietary-git, please keep in mind that you also need to replace the standard fprintd with fprintd-vfs_proprietary .

does not work with 138a:003f Validity Sensors, Inc. VFS495 (hp probook 430 g3) installed this package and libfprint-vfs_proprietary-git r15.685bc48-1

% fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
EnrollStart failed: Enroll start failed with error -103

янв 13 01:49:50 hpbook fprintd[7055]: capture-helper probably died while we were waiting for img ready signal
янв 13 01:49:50 hpbook fprintd[7055]: capture-helper output:
                                         SIGALRM caught: timed out waiting for VFS service
янв 13 01:49:50 hpbook fprintd[7055]: TRACE vfs_proprietary.c: vfs_proprietary_dev_activate() [229]
янв 13 01:49:50 hpbook fprintd[7055]: activation failed with error -103
янв 13 01:49:50 hpbook fprintd[7055]: failed to start enrollment

@fow0ryl :

1. Any reason you're using chrpath-svn instead of normal chrpath? I have to admit I only used the regular non-svn version, which is simply available from the community repository and doesn't need to be built.

2. If you're having problems with building openssl098, please report them to the maintainer of that package. I had no problems whatsoever, so perhaps there's an unlisted dependency of openssl098 that I happen to have installed. I know that lots of people who've already packaged the VFS daemon have created fake symlinks to 0.9.8 like you're doing in your PKGBUILD, but I don't see any benefit to that if the package explicitly requires a particular version of OpenSSL, and that version is still buildable and runnable.

3. If you have actually run into troubles caused by the missing files, I'll bring them back : the main reason why I chose to remove them is because the daemon ran fine without them - at least for me. Also, having random non-executable .bin files floating around in /usr/bin makes me want to shoot myself.

I'm unable to run this pkg for various reasons ...
- chrpath-svn failed, because the used link's are dead
- openssl098 failed to build

I think that the comment within the PKGBUILD is not helpful, since /usr/sbin is in fact only a link to /usr/bin. So the files /usr/sbin/HPUsbVFS[].img are copied to the right place in previous versions. Now the files are missing ...
# the stuff in /sbin doesn't seem used anywhere, although both the
# vcsFPService and validity-sensor binaries contain strings with paths to
# /usr/sbin/HPUsbVFS[].img . however, they have always been installed to
# /usr/bin via this package and it doesn't seem to have caused any issues, so
# I'm leaving them off for now.

So I decided to build my own pkg for the first testing.
I have changed chrpath to patchelf and replaced openssl098 by links to openssl lib's. Also changed vfs495 to vfs49x.

My PKGBUILD:

pkgname=vfs49x-daemon
realver=4.5-136.0
pkgver=${_realver//-/}
pkgrel=1
pkgdesc="Userspace driver for vfs49x fingerprint readers"
arch=('x86_64')
url=""
license=('unknown')
depends=('openssl' 'libusb-compat')
makedepends=('rpmextract' 'patchelf')
install='vfs49x-daemon.install'
provides=('vfs495-daemon')
 # source comes straight from the HP driver site for this laptop model, which
 # includes the vfs49x :
 # https://support.hp.com/us-en/drivers/selfservice/hp-probook-470-g0-notebook-pc/5350448
_softpaq='sp84530.tar'
source=("https://ftp.hp.com/pub/softpaq/sp84501-85000/${_softpaq}"
        'vfs49x-daemon.service'
        'vfs49x-sleep')
noextract=(${_softpaq})
md5sums=('9877c69c4f4b57a00f9e4afbcd9baacc'
         'ebe697d6fac43645191e2fad74bad99f'
         'a2edc66e120d073211f7ded3aeedd7d0')

prepare() {
  bsdtar xf "${_softpaq}" --strip-components 1
  rpmextract.sh Validity-Sensor-Setup-${_realver}.x86_64.rpm
# remove current rpath settings from given binary's
  patchelf --remove-rpath usr/bin/vcsFPService
  patchelf --remove-rpath usr/sbin/validity-sensor
  patchelf --remove-rpath usr/lib64/libvfsFprintWrapper.so
}
package() {
  cd "${srcdir}"
# install systemd files
  install -m 755 -D -t "${pkgdir}/usr/lib/systemd/system-sleep" vfs49x-sleep
  install -m 644 -D -t "${pkgdir}/usr/lib/systemd/system" vfs49x-daemon.service
#install readme
  install -m 644 -D -t "${pkgdir}/usr/share/doc/vfs49x-daemon" usr/share/doc/packages/validity/*
#install lib's
  install -D -t "${pkgdir}/usr/lib" usr/lib/libvfsFprintWrapper.so
#install binary's
  install -D -t "${pkgdir}/usr/bin" usr/bin/vcsFPService
#since sbin is a link to bin, we have to use bin instead of sbin .
  install -D -t "${pkgdir}/usr/bin/" usr/sbin/HP*
  install -D -t "${pkgdir}/usr/bin/" usr/sbin/validity-sensor
  install -D -t "${pkgdir}/usr/bin/" usr/sbin/ValiditySensorEventHandler
}

My vfs49x-daemon.install

post_install() {

#create links instead of installing openssl 0.9.8
  ln -s /usr/lib/libcrypto.so /usr/lib/libcrypto.so.0.9.8

  ln -s /usr/lib/libssl.so /usr/lib/libssl.so.0.9.8  
systemctl enable vfs49x-daemon.service
  systemctl start vfs49x-daemon.service
}
pre_upgrade() {
  systemctl stop vfs49x-daemon.service
  systemctl disable vfs49x-daemon.service
}
pre_remove() {
  systemctl stop vfs49x-daemon.service
  systemctl disable vfs49x-daemon.service
rm /usr/lib/libcrypto.so.0.9.8

  rm /usr/lib/libssl.so.0.9.8

}

the pkgbuild of the link skyeplus gave isnt working for me, because the download of sp62413.tar fails

Is there a way to make this work now that libfprint-git package dropped the Validity patch?

I'm pretty sure this only works with 495. Not sure if there are drivers for the other readers.

I can't enroll my fingerprint even after installing this package and libfprint-git. My notebook has Validity Sensors, Inc. VFS491, 138a:003d.

$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
Enrolling right-index-finger finger.
EnrollStart failed: Enroll start failed with error -1

$ journalctl -xe
[...]
jan 20 23:44:50 leet fprintd[19607]: user 'mylogin' claiming the device: 0
jan 20 23:44:50 leet fprintd[19607]: now monitoring fd 15
jan 20 23:44:50 leet fprintd[19607]: device 0 claim status 0
jan 20 23:44:50 leet fprintd[19607]: start enrollment device 0 finger 7
jan 20 23:45:10 leet Validity_vfs_wait_for_service[19607]: Validity device could not be found
jan 20 23:45:10 leet fprintd[19607]: enroll_stage_cb: result -1
jan 20 23:45:10 leet fprintd[19607]: no longer monitoring fd 15

@ikec Same issue with a VFS300 in a Dell Vostro 3500 (ID: 138a:0008)

@konfu Updated to a Github URL.