anything about this, i have the same problem.Quote:
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 do not know much about ubuntu but maybe there is anyway to disable the figerprint on this "unlock" and use regular password.
Thanks master_kernel :-)
Using your guide I have managed to get the Authentec 2501 fingerprint sensor working on my Lenovo 3000 N200 laptop running Intrepid!
Thanks once again.
for me worked fine.
This is my device Bus 002 Device 003: ID 08ff:1600 AuthenTec, Inc. AES1600
Everything worked fine until the point password chceks on menus such as network user and groups etc.
Also i could find the file gksu.py
Hi I have a motion m1400 tablet and it uses a authentec 2501. I actually contacted the fprint developers and they were able to add support for this device. I have the latest release version but I cannot figure out how to get the cvs or devel release that incorporates the code update to get the fix. Can anyone tell me how to get this for hardy heron. I dont know how to compile or build a deb. I can add a software source and follow directions.
i am trying to install fprint on my laptop. at the moment i've got problem with placing the two lines in the common.auth file. this is the file:
can somebody tell me where should i place those two lines?Code:
# /etc/pam.d/common-auth - authentication settings common to all services
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
# As of pam 1.0.1-5, this file is managed by pam-auth-update by default.
# To take advantage of this, it is recommended that you configure any
# local modules either before or after the default block, and use
# pam-auth-update to manage selection of other modules. See
# pam-auth-update(8) for details.
# here are the per-package modules (the "Primary" block)
auth [success=1 default=ignore] pam_unix.so nullok_secure
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
# end of pam-auth-update config
auth sufficient pam_fprint.so
auth required pam_unix.so nullok_secure.
Intrepid doesn't seem to like pam_unix.so, at least not in my tests.
Add the auth sufficient pam_fprint.so above the auth required pam_permit.so line. I added the nullok_secure to the existing required line:
auth required pam_permit.so nullok_secure
On occasion, it will ask for a password and then the fingerprint instead of one or the other...
Thinkfinger worked perfectly in Hardy but has a known bug in Intrepid where you have to press enter after a finger swipe. With that fixed, (http://www.thinkwiki.org/wiki/How_to...th_ThinkFinger) thinkfinger works much better than fprint. The only thing it is missing is a cool fingerprint enrollment gui.
I think I have a problem with the finger print reader after I resume from hibernation.
When I run fprint-demo I get the following message:
Also if I try to run a command using sudo I get this:Quote:
Status: could not open device
If I reboot then everything is fine.Quote:
aeslib:error [do_write_regv] bulk write error -2
fp:error [fp_dev_open] device initialisation failed, driver=aes2501
Any ideas anyone?
Thanks in advance.
The packages are included in Ubuntu 8.10, I guess the guide should be updated for that.