Bug 1191926 - VFS495 Fingerprint Reader Not found by fprint
Summary: VFS495 Fingerprint Reader Not found by fprint
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: libfprint
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1322555
TreeView+ depends on / blocked
 
Reported: 2015-02-12 09:16 UTC by tibs245
Modified: 2017-03-12 19:40 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: libfprint no detect VFS495 fingerprint Consequence: I can't use my fingerprint Fix: Result: Device not found
Clone Of:
: 1322555 (view as bug list)
Environment:
Last Closed: 2016-09-15 16:00:44 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description tibs245 2015-02-12 09:16:50 UTC
Description of problem:


Version-Release number of selected component (if applicable):
I have Fedora 21 with last update at this day. My FringerPrint Reader ( VFS495 ) is not found by fprint :

Exemple :
$ fprintd-enroll 
list_devices failed: No devices available

$ lsusb  | grep Fingerprint
Bus 003 Device 005: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

I have test with official libfprint and experimental version :
$ yum info libfprint
Installed Packages
Name        : libfprint
Arch        : x86_64
Version     : 0.6.0
Release     : 1.fc21
Size        : 474 k
Repo        : installed
From repo   : updates-testing
Summary     : Toolkit for fingerprint scanner
URL         : http://www.freedesktop.org/wiki/Software/fprint/libfprint
License     : LGPLv2+
Description : libfprint offers support for consumer fingerprint reader devices.


How reproducible:
Try detect VFS95 Fingerprint

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Ned 2015-07-29 13:06:43 UTC
Hello, 

Same issue on HP Probook 650G1 laptop running F22(64)Mate-Compiz : 
same fingerprint reader, same result for both "fprintd-endroll" and "lsusb" commands.

note that there is a "4" missing in "How reproducible" section of initial post. The model is VFS495

Comment 2 Fedora End Of Life 2015-11-04 10:33:15 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Brian J. Murrell 2015-11-04 12:14:03 UTC
This issue still exists in F22.  Can somebody please update the Version: field?  Thanks.

Comment 4 Ned 2015-11-09 08:11:16 UTC
This issue still exists also in F23, so like Brian J. Murell I wish the version field be updated

Comment 5 Paul Jakma 2015-11-23 09:26:09 UTC
This issue still exists in F23 with fprintd-0.6.0-3.fc23.x86_64:

$ fprintd-list paul
No devices found

$ lsusb | grep -i finger
Bus 007 Device 002: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader

Comment 6 Brian J. Murrell 2015-11-23 11:58:30 UTC
This is a request to please update the Version: field of this ticket to F23 since this still exists in F23 and my request in comment #3 back on 2015-11-04 to update to F22 was even ignored.

This ticket should not EOL just because F21 is EOLing since this issue continues to exist.  Please don't ignore this request to update the Version: field.

Comment 7 emoziko 2015-11-25 18:26:49 UTC
Exactly same problem here.. 

Fedora 23 x64
reader: VFS495

Comment 8 Janis 2015-11-25 22:47:36 UTC
The same problem here. HP Envy Bang & Olufsen

uname -r
4.2.5-300.fc23.x86_64

fprintd-0.6.0-3.fc23.x86_64
fprintd-pam-0.6.0-3.fc23.x86_64

fprintd-enroll
list_devices failed: No devices available


Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               1.10
  bDeviceClass          255 Vendor Specific Class
  bDeviceSubClass        16 
  bDeviceProtocol       255 
  bMaxPacketSize0         8
  idVendor           0x138a Validity Sensors, Inc.
  idProduct          0x0050 Swipe Fingerprint Sensor
  bcdDevice            0.60
  iManufacturer           0 
  iProduct                0 
  iSerial                 1 b716dfb07643
  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
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

Comment 9 Brian J. Murrell 2015-11-26 11:36:09 UTC
@Janis: why did you clear the needinfo flag for Bastien?  It was there for him to change the version of this ticket to 23 since that's the latest version that this is being seen in.

Although I'm about to give up on waiting for him and escalate this request to Red Hat management since he does not seem to be responding.

Comment 10 Pierre-YvesChibon 2015-11-26 13:32:35 UTC
If you say it's valid for F23, just edit the field yourself :)

Comment 11 Brian J. Murrell 2015-11-26 15:19:36 UTC
(In reply to Pierre-YvesChibon from comment #10)
> If you say it's valid for F23, just edit the field yourself :)

If only I could.  I don't have permission to.  I suspect outside of Red Hat only the reporter and the assignee can.

Comment 12 Pierre-YvesChibon 2015-11-26 15:46:16 UTC
Apparently I can, so here it is :)

Comment 13 Brian J. Murrell 2015-11-26 15:54:54 UTC
(In reply to Pierre-YvesChibon from comment #12)
> Apparently I can, so here it is :)

Awesome!  Thanks!

I wonder why you can but I cannot.

Comment 14 Juan A. Burgos 2015-12-03 17:37:21 UTC
Apparently SUSE got this patched already.

https://www.suse.com/support/update/announcement/2013/suse-ru-20131363-1.html

Comment 15 Florian Braun 2016-01-14 08:52:08 UTC
Have exactly the same Problem , found a dirty "Workaround" by self making libfprint but could not get it to work:https://github.com/Gnate/libfprint/tree/master/libfprint/drivers/validity

Comment 16 Andrew Wasielewski 2016-03-27 18:19:51 UTC
Same here on Fujitsu Lifebook T935 in Fedora 23 (kernel 4.4.6-300.fc23.x86_64) with fprintd 0.6.0-3.

Bus 001 Device 008: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor

Comment 17 Marlin Whitaker 2016-06-04 19:12:56 UTC
And same here on HP EliteBook Folio 1040 G3 running Fedora 24 beta.

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

Comment 18 Oleksandr Tarasiuk 2016-07-21 15:18:28 UTC
The same on HP ProBook 470. FC24.

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

Comment 19 Gijs Roeffen 2016-08-01 12:59:39 UTC
The same on a HP Elitebook 850 G2. 

The guide on this page: https://balintbanyasz.wordpress.com/2015/03/27/get-validity-vfs-495-fingerprint-reader-working-in-ubuntu-14-04/ explains it for Ubuntu systems whereas afterwords it works (tested). Hopefully i can compile something togheter for Fedora 24.

Comment 20 Jared Smith 2016-08-30 18:30:49 UTC
Same on the HP ZBook 15 G3 on Fedora 24.

Clearing the needinfo flag, as the information has obviously been provided.

Comment 21 Bastien Nocera 2016-09-15 16:00:44 UTC
The device is not support by libfprint upstream, and the hardware maker hasn't provided any specifications, just a bunch of binary blob drivers[1].

This makes it impossible to support. Please file a bug upstream if you want this fixed, bearing in mind that nothing will happen unless specs become available.

[1]: such as the ones in https://bugs.freedesktop.org/show_bug.cgi?id=973461

Comment 22 Robert Krátký 2016-11-06 12:33:22 UTC
Just a correction: the URL of the upstream bug is https://bugs.freedesktop.org/show_bug.cgi?id=97346


Note You need to log in before you can comment on or make changes to this bug.