Bug 672520

I also purchased a Dell Vostro 3500 two days ago, and the fingerprint is not working:

german@skytux ~ $ lsusb | grep -i persona
Bus 001 Device 004: ID 138a:0008 DigitalPersona, Inc

german@skytux ~ $ rpm -qa | grep fprint
fprintd-pam-0.2.0-2.fc14.x86_64
fprintd-0.2.0-2.fc14.x86_64
fprint_demo-0.4-6.fc12.1.x86_64
libfprint-0.3.0-1.fc14.x86_64

Germán.

There is a first patch for libfprint available here:
https://bugs.launchpad.net/bugs/285089

Works quite well on Fedora 14. I probably broke some other readers functionality, but got it working by


1. upgrading the system with the latest updates from the "fedora"-repository

2. forcing a removal of the original libfprint via
   "rpm -e nodeps libfprint-hateverversion"

3. choosing a very basic configuration "autoreconf --prefix=/usr"

4. "make && make install"...

5. "ldconfig" and... there it is!

Just enroll your fingerprint using the "fprint_demo" package.

Created attachment 481798 [details]
Patch for libfprint-0.3.0

Created attachment 481799 [details]
libfprint working with the patch mentioned

Worth following:

http://lists.reactivated.net/pipermail/fprint/2011-March/001748.html

The driver's been developed. It requires some testing etc. 

Thanks,
Ankur

Tobias, the discussions about hardware support should go upstream. Post your patch there, discuss it with people already working on the driver.

(In reply to comment #4)
> Created attachment 481799 [details]
> libfprint working with the patch mentioned

Tobias:

I removed the old package and compiled this one with the patch. The result when I open fprint_demo is: no devices fond :(

Ideas?

Germán.

Hi German

What version of fprint_demo did you use? Or: was it the fprint_demo from the fedora repository?

Tobias

(In reply to comment #8)
> Hi German
> 
> What version of fprint_demo did you use? Or: was it the fprint_demo from the
> fedora repository?
> 
> Tobias

Yes, from Fedora repos:

german@skytux ~ $ rpm -q fprint_demo
fprint_demo-0.4-6.fc12.1.x86_64

Germán.

Ok, I am using the same package on my system, so that one should work.
Here's what I did:

1. removed the libfprint-package installed on the system regardless of possible broken dependancies (at your own risk..!)
2. configured the patched libfprint sources to be installed where the repository-fprint tools expect the library to be (--prefix=/usr)
3. compiled and installed the package
4. double-checked there are no broken library paths (symlinks..) by looking at the output of ldd /usr/bin/fprint-WHATEVER
5. run fprint_demo with root priviledges in order to be allowed to access the device 

Tobias

Tobias: it doesn't work for me :(

German,
did you try compiling the version and patch attached to this bugreport?

Tobias:

I have downloaded the attachment from your comment 4, using Fedora 14, and it didn't work. Now I have Fedora 15, I have enabled updates-testing repos and installed the following versions:

german@skytux ~ $ rpm -qa | grep fprint
fprintd-0.4.1-1.fc15.x86_64
fprintd-pam-0.4.1-1.fc15.x86_64
fprint_demo-0.4-7.fc15.1.x86_64
libfprint-0.4.0-1.fc15.x86_64

and even the new versions installed, libfprint still doesn't work on my system.

the patch attached seem to have been merged in libfprint in late March, however, the commit log mentions:

    Author: Sergio Cerlesi <sergio.cerlesi>
    Date:   Wed Mar 30 14:20:22 2011 +0200

        Added support for Validity VFS101
    
        USB ID 138a:0001

The USB id differ from the one in this issue.

btw, it is not needed to override the system package. It can be trivially done with LD_LIBRARY_PATH-fuu:

# LD_LIBRARY_PATH=$PWD/libfprint/.libs/ /usr/bin/fprint_demo

upstream issue: https://bugs.freedesktop.org/show_bug.cgi?id=37574

(In reply to comment #12)
> German,
> did you try compiling the version and patch attached to this bugreport?

Hi Tobias:

Sorry that I insist on this, but this time I used the spec file from Fedora to compile the program (libfprint-0.3.0) and to apply the patch... but it still gives the damn "Status: No devices found" message when running fprint_demo as root. I removed the installed version of libfprint with "rpm -e --nodeps" as you said before... any thoughts??

This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

(In reply to comment #14)
> the patch attached seem to have been merged in libfprint in late March,
> however, the commit log mentions:
> 
>     Author: Sergio Cerlesi <sergio.cerlesi>
>     Date:   Wed Mar 30 14:20:22 2011 +0200
> 
>         Added support for Validity VFS101
>     
>         USB ID 138a:0001
> 
> The USB id differ from the one in this issue.

That'd be because it the one mentioned in this issue uses the VFS301 driver, not the VFS101 driver.

The VFS301 driver is in libfprint 0.5.0 which is in Fedora 17 and Fedora 18.