ID 138a:003f Validity Sensors, Inc. on HP EliteBook 840G1

Bug #1397067 reported by Victor J. C. Geyer on 2014-11-27
304
This bug affects 61 people
Affects Status Importance Assigned to Milestone
libfprint (Ubuntu)
Undecided
Unassigned

Bug Description

The libfprint package does not seem to recognize the Validity Sensor

OS: Ubuntu 14.10 LTS 64 bits
Kernel: 3.16.0-25-generic #33-Ubuntu SMP
Hardware: HP Elitebook 840G1
lsusb output:
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0424:5534 Standard Microsystems Corp.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 04f2:b3ed Chicony Electronics Co., Ltd
Bus 002 Device 004: ID 138a:003f Validity Sensors, Inc.
Bus 002 Device 003: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 002 Device 006: ID 8087:07dc Intel Corp.
Bus 002 Device 002: ID 0424:2134 Standard Microsystems Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

When running both the Fingerprint GUI, the device is not recognized.

Will the be included as a supported device anywhere in the future?

Thank you.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libfprint (Ubuntu):
status: New → Confirmed
David Pérez (sanete) wrote :

In my case it is a HP Probook 650 G1 notebook.

Mischa (mischa-courtin) wrote :

I have the same issue on my HP Elitebook 850, running Ubuntu LTS 14.04

Bus 002 Device 004: ID 138a:003f Validity Sensors, Inc.
Couldn't open device, some information will be missing
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 255 Vendor Specific Class
  bDeviceSubClass 18
  bDeviceProtocol 255
  bMaxPacketSize0 8
  idVendor 0x138a Validity Sensors, Inc.
  idProduct 0x003f
  bcdDevice 1.04
  iManufacturer 0
  iProduct 0
  iSerial 1
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 46
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 100mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 4
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 0
      bInterfaceProtocol 0
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0008 1x 8 bytes
        bInterval 4

Ales (w-ales) wrote :

HP ProBook 450 G2 J4S01EA#BCM
Bus 002 Device 004: ID 138a:003f Validity Sensors, Inc.

Aderik Teekman (aderik) wrote :

HP ProBook 650 G1
Bus 003 Device 003: ID 138a:003f Validity Sensors, Inc.

skaggel (skaggel) wrote :

HP Probook 430 G2
Bus 002 Device 003: ID 138a:003f Validity Sensors, Inc.

mboron83 (mboron83) wrote :

HP Probook 640 G1
Bus 003 Device 003: ID 138a:003f Validity Sensors, Inc.

Mauro (mauromol) wrote :

Me too with a HP ProBook 450 G1.

iceman75 (javier-orejarena) wrote :

Me too, HP Probook 645 (G1)

Bus 005 Device 002: ID 138a:003f Validity Sensors, Inc.

Robert Ebers (robert-ebers) wrote :

Same issue on the Dell Latitude E5540
Bus 001 Device 005: ID 138a:003f Validity Sensors, Inc.

I have the same problem too, HP Probook 450 G2
Bus 002 Device 003: ID 138a:003f Validity Sensors, Inc.

It would be nice to support it.

BOPOHA (anatolii.vorona) wrote :

HP Probook 430 (G2)
Bus 002 Device 003: ID 138a:003f Validity Sensors, Inc.

I have the same issue on my HP Elitebook Folio 1040, running Ubuntu LTS 14.04 64 bits
Bus 002 Device 003: ID 138a:003f Validity Sensors, Inc.

HP EliteBook 820 G1 affected as well.

Bus 002 Device 004: ID 138a:003f Validity Sensors, Inc.

Anshu Prateek (anshu-prateek) wrote :

Same issue for HP Probook 450 G2.
Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

Oliver (grimmoliver) wrote :

Same issue on my HP EliteBook 840, Ubuntu 15.04, where the sensor is not recognized for logging in:

Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc.

Sensor is predictably recognized by Windows 7 on the same computer. Would be great if it could also be supported on Linux.

Taras Vykhovanskyi (b88lviv) wrote :

Found this:
https://balintbanyasz.wordpress.com/2015/03/27/get-validity-vfs-495-fingerprint-reader-working-in-ubuntu-14-04/

but I'm not able to do the same things

when I run:

vykh@vykh-mint ~ $ sudo /etc/init.d/vcsFPServiceDaemon start

I get this:

/etc/init.d/vcsFPServiceDaemon: 36: /etc/init.d/vcsFPServiceDaemon: rc_reset: not found
Starting vcsFPService Daemonnohup: ignoring input and redirecting stderr to stdout
nohup: failed to run command ‘/sbin/startproc’: No such file or directory
/etc/init.d/vcsFPServiceDaemon: 49: /etc/init.d/vcsFPServiceDaemon: rc_status: not found
/etc/init.d/vcsFPServiceDaemon: 113: /etc/init.d/vcsFPServiceDaemon: rc_exit: not found

and i googled this:
: It’s specific to whatever distribution you’re running. Debian and Ubuntu have /lib/lsb/init-functions; SuSE has /etc/rc.status; none of them are compatible with the others.

can You give any advise?

Same here - Dell Latitude E5440
Bus 001 Device 008: ID 138a:003f Validity Sensors, Inc.
Not recognized by Fingerprint GUI 1.06

Newton Kitonga (nknganda) wrote :

Same problem with HP Zbook 15 2014

vruohonen (v-ruohonen) wrote :

Same here with HP Elitebook Folio 1040 G2

JKOOL (jkool) wrote :

Same here, HP Folio 1040 G2

Ahmad Amr (aamr) wrote :

HP zBook 14 138a:003f :(

HP EliteBook 840, Ubuntu GNOME 15.10.

Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

SqUe (sque) wrote :

HP Probook 440 G3

Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

Cesar (c7sar) wrote :

HP ZBook 14
Bus 001 Device 003: ID 138a:003f Validity Sensors, Inc.

Luca Giovenzana (lucagiove) wrote :

HP EliteBook 840 G2

Philip Collins (pa-collins) wrote :

HP ZBook 17
Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

(Manjaro 15.12, KDE plasma 5.5.3, Kernel 4.1.16)

oOSephirothOo (sephiroth-naxo) wrote :

Same issue on the Dell Latitude E5540
Bus 003 Device 008: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

one more
HP Probook 430 G2
Bus 002 Device 003: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

Greg (senykg) wrote :

Lattitude E5440
same issue
Bus 003 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

HP Probook 450 G2
Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader
It would be great if this is supported

Alex (alstef) wrote :

HP Probook 450 G2
Bus 002 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

Thanks!

Igor (cryptor1) wrote :

Same device ID: Validity Sensors, Inc. VFS495 Fingerprint Reader.
HP ProBook 470 G3.

disco (discohr) wrote :

HP Probook 470 G3
Bus 001 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

igelhorst5000 (rkaiser) wrote :

Same issue: HP Elitebook 840 G3

Janos Kovacs (kovijanny) wrote :

HP ProBook 450 G4

Bus 001 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

fprintd-enroll
list_devices failed: No devices available

Tudor (tudorgergely) wrote :

Same issue: HP Probook 440 G4
Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

rahulchopde (rahulchopde) wrote :

same issue for HP Probook 440 G3

Bus 001 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

tothsoft@gmail.com (tothsoft) wrote :

/etc/init.d/vcsFPServiceDaemon ...you must completly overwrite for ubuntu system:

#!/bin/sh
### BEGIN INIT INFO
# Provides: Validity Fingerprint Service Daemon
# Required-Start: $remote_fs $syslog
# Required-Stop: $remote_fs $syslog
# Default-Start: 2 3 5
# Default-Stop: 0 6
# Short-Description: Validity Fingerprint Service Daemon
# Description: Start vcsFPService to provide Validity FP Service
### END INIT INFO
#
# Note on runlevels:
# 0 - halt/poweroff 6 - reboot
# 1 - single user 2 - multiuser without network exported
# 3 - multiuser w/ network (text mode) 5 - multiuser w/ network and X11 (xdm)
#

. /lib/lsb/init-functions

vcsFPService_BIN=/usr/bin/vcsFPService
test -x $vcsFPService_BIN || { echo "$vcsFPServiceDaemon is not installed";
if [ "$1" = "stop" ]; then exit 0;
else exit 5; fi; }

case "$1" in
start)
echo -n "Starting vcsFPService Daemon \n"
start-stop-daemon --start --background --quiet --exec "$vcsFPService_BIN" > /dev/null 2 >&1

;;
stop)
echo -n "Stopping vcsFPService Daemon \n"

#/sbin/killall -TERM $vcsFPService_BIN
start-stop-daemon --stop --quiet --quiet --oknodo --retry=0/1/KILL/5 --exec "$vcsFPService_BIN" > /dev/null 2 >&1

;;
status)
echo "Checking for vcsFPService Daemon \n"

if pidof -o %PPID $vcsFPService_BIN> /dev/null; then
echo "client is running. \n"
exit 0
else
echo "client is not running. \n"
exit 1
fi
;;
*)
echo "Usage: $0 {start|stop|status}"
exit 1
;;
esac

exit 0

tothsoft@gmail.com (tothsoft) wrote :

sudo fprint_demo

Sensor usb#vid_138a#pid_0007#0020ea9cXXXX plugged. (my comment:sorry last numbers XXXX of id number are hidden ..for sure)

Waiting for finger swipe ...

tothsoft@gmail.com (tothsoft) wrote :

Guys, ...vfs451 is going :D ..ubuntu 16.04 with my prepared packages ...yeah,,...so happy

tothsoft@gmail.com (tothsoft) wrote :

In my prepared packages are also drivers for sensors as vfs451, 471,491, 495 ..ob base of guide: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1397067

tothsoft@gmail.com (tothsoft) wrote :

Enjoy, ..and please develop something more user friendly for ubuntu users with this drivers (i am not IT expert, only user with elitebook 8540w):D

https://mega.nz/#!J0FDDZBa!33t8z9wdZQ3OGfQ8VvEC-H5tp6pWgxg5LyN0klnOYaE

Igor (cryptor1) wrote :

@tothsoft doesn't help in my case... I have HP ProBook 470 G3 and VFS495 fingerprint reader.
There are no messages after "sudo fprint_demo" in my case. "fprint project demo" window is opened with message "Status: No devices found" at the bottom.

Mina (842mono) wrote :

Got it working on "HP Probook 450". It has "138a:003f" "VFS 495". See this: https://askubuntu.com/a/924475/174392

Igor (cryptor1) wrote :

@Mina this solution didn't help https://askubuntu.com/a/924475/174392. I've just installed a lot of garbage in my system expecting it to work. There was no 'fprint-demo_0.4-1_amd64.deb' file. '/etc/init.d/vcsFPServiceDaemon' is a text file in my case (if it matters) and finished with this message:
/etc/init.d/vcsFPServiceDaemon: 33: .: Can't open /etc/rc.status
and 'sudo: fprint_demo: command not found'.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers