HOWTO: Fingerprint reading in Ubuntu with fprint

[master_kernel]

Getting your fingerprint reader to work in Ubuntu

Project fprint homepage: http://reactivated.net/fprint/wiki/Main_Page
Packages for fprint: http://www.madman2k.net/comments/105

The fprint project aims to plug a gap in the Linux desktop: support for consumer fingerprint reader devices. Previously, Linux support for such devices has been scattered amongst different projects (many incomplete) and inconsistent in that application developers would have to implement support for each type of fingerprint reader separately. For more information on where we came from, see the project history page. We're trying to change that by providing a central system to support all the fingerprint readers we can get our hands on. The software is open source and in the long term we're shooting for adoption by distributions, integration into common desktop environments, etc.

Note: These instructions are intended for Ubuntu Jaunty.

First off, remember that fprint is not entirely stable, and may not work all the time. A list of supported devices is here, and the list of unsupported devices is here.



1. Next, update your sources and install fprint:

sudo apt-get update
sudo apt-get install fprint-demo libfprint-dev libfprint0 libpam-fprint aes2501-wy

2. Now you can enroll your fingers using either the terminal or a graphical user interface.
Terminal:

pam_fprint_enroll

GUI:

fprint_demo

3. Last thing to do is configure PAM so that the fingerprint reader can be useful. Open up your PAM authentication file and edit it:

sudo gedit /etc/pam.d/common-auth

4. If you want the fingerprint to be sufficient, add this at the top of the commands (do it multiple times for however many attempts you want to allow):

auth sufficient pam_fprint.so

Use this if you want to require the fingerprint and the password.

auth required pam_fprint.so

5. For programs using gksudo/gksu, you should get the wrapper attached to this post and to add fingerprint support and enter the following code:

sudo mv ./gksu.py /usr/local/bin/gksu
sudo chmod 755 /usr/local/bin/gksu
sudo apt-get install python-gnome2-extras python-pexpect

7. Enjoy your fingerprint reader support!

Steps 4 and 5 tell Ubuntu to check your fingerprint, and if that fails, then ask your password. This rule has some exceptions, one that I have encountered is on the login screen. I have to scan my fingerprint before typing my password. One thing I did notice is that when you use sudo in the terminal, it asks for your fingerprint, which I thought was pretty cool. One disadvantage is that anything using gksu does not seem to work properly, specifically because it does not tell you to scan your finger when needed.

Troubleshooting:
The one problem I ran into when using fprint was that I could not run fprint_demo without sudo. It failed with the error message below:

uru4000:error [dev_init] interface claim failed fp:error [fp_dev_open] device initialisation failed, driver=uru4000

I decided to post my problem here on the forums.
Here is the solution. You have to add yourself to the plugdev group and then change the permissions of the usb folder to allow access to the plugdev group. You can verify you are in the plugdev group by using groups:

sudo usermod -a -G plugdev $USER
groups | grep plugdev       # Make sure there is output from this
sudo chgrp -R plugdev /dev/bus/usb/

Then try running fprint_demo, and hopefully it will work:

fprint_demo

[Evil Wayz]

Everything works fine for me UNTIL i try to enroll, and then it tells me no device found. I knwo it's there because it shows up in verbose mode bootup. Help?

[Gotterdammerung]

Originally Posted by Evil Wayz Everything works fine for me UNTIL i try to enroll, and then it tells me no device found. I knwo it's there because it shows up in verbose mode bootup. Help?

Same problem here...

[master_kernel]

Originally Posted by Evil Wayz Everything works fine for me UNTIL i try to enroll, and then it tells me no device found. I knwo it's there because it shows up in verbose mode bootup. Help?

Try following the steps in troubleshooting to fix this.

[Nurionn]

Thanks, that worked almost perfect for me.

I have only one problem: Since I installed my fingerprint reader, I cannot change network or user settings using the GUI.
If I click on "Unlock" the window freezes for ~20sec and then it shows an error message saying approximately: "authentification failed! an unexpected error has occurred." (German version: "Authentifizierung fehlgeschlagen! Es ist ein unerwarteter Fehler aufgetreten.")

Has anyone an idea?

[master_kernel]

Originally Posted by Nurionn Thanks, that worked almost perfect for me. I have only one problem: Since I installed my fingerprint reader, I cannot change network or user settings using the GUI. If I click on "Unlock" the window freezes for ~20sec and then it shows an error message saying approximately: "authentification failed! an unexpected error has occurred." (German version: "Authentifizierung fehlgeschlagen! Es ist ein unerwarteter Fehler aufgetreten.") Has anyone an idea?

This is just one of the bugs in fprint; I get this error too. If you find a fix, let me know.

[chase809]

Originally Posted by Nurionn Thanks, that worked almost perfect for me. I have only one problem: Since I installed my fingerprint reader, I cannot change network or user settings using the GUI. If I click on "Unlock" the window freezes for ~20sec and then it shows an error message saying approximately: "authentification failed! an unexpected error has occurred." (German version: "Authentifizierung fehlgeschlagen! Es ist ein unerwarteter Fehler aufgetreten.") Has anyone an idea?

I was having the same problem until I realized that I can insert the

auth sufficient pam_fprint.so

into any pam.d file. So instead of entering this into the common-auth which is pulled by most files/auth methods I insert this line into the functions I wish to have my finger reader. For example if I want my finger reader to unlock my screensaver I inserted it into the gnome-screensaver (above the include common-auth section). The final product looks like this.

auth sufficient pam_fprint.so
@include common-auth
auth optional pam_gnome_keyring.so

Now my finger reader works for just my gnome-screensaver and doesn't cause my policy kit to lock up. I have a feeling the pam_fprint.so has not been developed for the new policy kit in 8.04. Hope this helps, you can explore with different pam.d files and turn the finger reader on or off.

[emecas]

Hey thanks chase809

I was looking long time for the causes about that problem

A real help that appear like a surprise and in a place looking for other subject..

http://ubuntuforums.org/showthread.p...54#post6307354

Originally Posted by chase809 I was having the same problem until I realized that I can insert the auth sufficient pam_fprint.so into any pam.d file. So instead of entering this into the common-auth which is pulled by most files/auth methods I insert this line into the functions I wish to have my finger reader. For example if I want my finger reader to unlock my screensaver I inserted it into the gnome-screensaver (above the include common-auth section). The final product looks like this. auth sufficient pam_fprint.so @include common-auth auth optional pam_gnome_keyring.so Now my finger reader works for just my gnome-screensaver and doesn't cause my policy kit to lock up. I have a feeling the pam_fprint.so has not been developed for the new policy kit in 8.04. Hope this helps, you can explore with different pam.d files and turn the finger reader on or off.

[moob]

Originally Posted by master_kernel Try following the steps in troubleshooting to fix this.

I have similar problem like Evil Wayz has. I was googling in I-mess. But i still can't find reason.
I know that my fprintreader is working propertly (i used it in Vista).
When I type su:

Could not locate any suitable fingerprints matched with available hardware.

pam_fprint_enroll:

No devices detected.

What kind of information do you need from my side?
Thank you.

[Gotterdammerung]

up