Fingerprint GUI

A place to discuss issues of the Fingerprint GUI.

You can subscribe to this discussion group using an RSS feed reader.

System 76 Laptop: FingerprintGUI 0.12

It won't let me scan, keeps saying
Fingerprint Fail!
"Fingerprint was not saved.  Click "No" to retry.  Select another finger.  If I say No, the dialog reappears in a fraction of a second.  If I say yes it takes me to the previous menu, that lets me select a finger, but it always results in the same "Fingerprint was not saved" dialog.

Fingerprint device is a Uptek (0x147e) Biometric Touchchip/Touchstrip Fingerprint Sensor (0x1000)
Permalink Gary C 
March 14th, 2010 4:23am
Please post a log output here.

W.U.
Permalink Wolfgang Ullrich 
March 14th, 2010 10:50am
Hey, I had the same problem and I got it to work with following:
------------------------
step 11
$ lsusb

ID 147e:1000, ist der fingerprint device. Dort steht weiter keine andere Info.
Aber wenn ihr folgendes ergänzt:
step 11a
$ lsusb -v -d 147e:1000

Dann steht bei iManufacturer: Touchstrip und bei iProduct: Fingerprint sensor.
Nun müßt ihr das was links vom ID 147e:1000 steht (Bus xxx Device xxx) merken.
Diese Angaben ändern sich nach jedem Neustart!
step 12
$ sudo chmod 777 /dev/bus/usb/xxx -R

Das ‘xxx’ ist die Bus Adresse (nicht Device)die ihr euch gemerkt habt!
---------------------
Link: http://n10j.wordpress.com/2009/02/14/ubuntu-810-fingerprint-einrichten/

If you have problem with reading and understanding cause its german, I would try to translate it to english.
Permalink Florian Stallmann 
March 15th, 2010 11:47pm
I've got exactly the same problem with fingerprintGUI 0.12 with the Upek 147e:1000 fingerprint scanner.

I'm running Arch Linux X64 with libfprint 0.0.6-4.

Unfortunately, the solution posted above me doesn't work for me. I'e also tried running the fingerprintGUI as root.

The debug option doesn't create a logfile for me, though I have the syslog-ng deamon running:
[dennis@archie bin]$ ./fingerprintGUI --debug
[dennis@archie bin]$ cd /var/log
[dennis@archie log]$ ls
ConsoleKit  dmesg.log  faillog  lastlog  Xorg.0.log

Funny note: when I get the error and press the Esc button, the error disappears, leaving me at the scan tab without any error, while pressing the "no" button (retry scan) will immediately reopen the error window.

If you need any outputs or tests performed by me, let me now.
Permalink Dennis Groenen 
March 16th, 2010 9:39am
Oh sorry, the important thing I've done could be the following:

cd /lib/udev/rules.d
sudo cp 40-libfprint0.rules /etc/udev/rules.d/
cd /etc/udev/rules.d/
sudo mv 40-libfprint0.rules 91-libfprint0.rules

Add 2 lines at the end of the file:
# Device upek
ATTRS{idVendor}==”147e”, ATTRS{idProduct}==”1000″, MODE=”0664″, GROUP=”plugdev”

Btw: I'm using Ubuntu 9.10 64-bit on an acer travelmate 5730.

Hope this helps.
Permalink Florian Stallmann 
March 16th, 2010 10:50am
Thank you for your reply.

I've added the two lines to /etc/udev/rules.d/70-fprint.rules. /lib/udev/rules.d/XX-fprint.rules didn't exist in my filesystem, but that shouldn't be a problem as the rule files in /etc/ have precedence over the files rules files in /lib/

Unfortunately the added lines didn't fix the error for me. I've tried chmodding /dev/bus/usb/002 and running the fingerprintGUI as root again as well.

The only thing I've changed from your 2 lines is replacing the group plugdev to scanners (which my user is a member of, of course)
Permalink Dennis Groenen 
March 16th, 2010 11:43am
Hmm, at the install.pdf it says, that you have to rename the file from XX-libfprint0.rules to 91-libfprint0.rules . But no idea if this makes a difference.

Sorry I have no more ideas for now.
Permalink Florian Stallmann 
March 16th, 2010 7:01pm
Please check your syslog settings and find out where the "auth" log output goes to. Log output is important for me to find out what's going wrong there.

The hint about changing the filename "XX-libfprint0.rules" to "91-libfprint0.rules" was given because I've found that on some systems the order of "*.rules" files in "/etc/udev/rules.d/" matters.

W.U.
Permalink Wolfgang Ullrich 
March 17th, 2010 9:42am
Okay, apparently there were some problems with my syslog-ng installation, but I've got it fixed now.

Content of /etc/udev/rules.d/91-libfrint0.rules:
[...]
# Upek
ATTRS{idVendor}=="147e", ATTRS{idProduct}=="1000", MODE="0664", GROUP="scanner"

The content of /lib/udev/rules.d/40-fprint.rules is exactly the same as the rules file in /etc

Commands I have executed:
[dennis@archie bin]$ cat /etc/group | grep scanner
scanner:x:96:dennis
[dennis@archie ~]$ cd /usr/local/bin/
[dennis@archie bin]$ sudo chmod 777 /dev/bus/usb/002 -R
[dennis@archie bin]$ ./fingerprintGUI

Auth.log: http://pastebin.org/115987

When running fingerprintGUI as root, the auth.log shows exactly the same error as when I ran it as a normal user.
Permalink Dennis Groenen 
March 17th, 2010 11:00am
Here we have the problem:
> ABSOpen() failed -1086

It's a problem with the proprietary upek driver (libbsapi.so). Unfortunately there is no description for this error (-1086).
Mabe your device needs the "NVM emulation". Please have a look into this document:
http://www.n-view.net/Appliance//fingerprint/BSAPIUsageonLinux.pdf

Try to setup the emulation for your device.

W.U.
Permalink Wolfgang Ullrich 
March 17th, 2010 3:13pm
Setting up the NVM emulation caused fingerprintGUI not to directly display the error, but after a second or two. Auth.log now shows a different error.

Commands I have executed:
[dennis@archie bin]$ sudo mkdir /var/upek
[dennis@archie bin]$ sudo chmod 777 /var/upek
[dennis@archie bin]$ sudo chmod 777 /dev/bus/usb/002 -R
[dennis@archie bin]$ ./fingerprintGUI

auth.log: http://pastebin.org/116531

Also, /var/upek/ now contains a 16KB .bin file

Some have been able to fix this error by creating the XX-libfprint0.rules file, but on my system the file is already there.

I'll keep trying getting the reader to work using different permissions and setups. If I may find a solution, I'll post it here.
Permalink Dennis Groenen 
March 17th, 2010 9:30pm
> Setting up the NVM emulation caused fingerprintGUI not to directly display the error, but after a second or two. Auth.log now shows a different error.

Yes. This one:

ABSOpen() failed -1057 (Fingerprint sensor device communication error.)

In some cases I've seen that removing all *.bin files in /var/upek/ did help. Try it.

In other cases there was some other process which had held open the device (e.g. a virtual machine running Windows on that host).

W.U.
Permalink Wolfgang Ullrich 
March 18th, 2010 11:06am
Removing the .bin file didn't solve the problem.

I also got no software running that is using the fingerprint reader as far as I know.
Permalink Dennis Groenen 
March 19th, 2010 5:27pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics