[fprint] Weird problem with screensaver

[Daniel Hauck]

I don't lock my screen that often but I have noticed a weird problem.

When I was using thinkfinger, I did not have this issue.  I could move
the mouse and get prompted for password or fingerprint.  (I am using
Xscreensaver)

But now that I am using fprint, when I go to unlock my machine using
fingerprint authentication (which is the only option) it needs to go
through the entire time sequence before it will accept it.


Is there some configuration option I should change to make it work like
it did with thinkfinger?

here is my /etc/pam.d/system-auth

]$ cat /etc/pam.d/system-auth
#%PAM-1.0
# This file is auto-generated.
# User changes will be destroyed the next time authconfig is run.
auth        required      pam_env.so
auth        sufficient    pam_fprint.so
auth        sufficient    pam_unix.so nullok try_first_pass
auth        requisite     pam_succeed_if.so uid >= 500 quiet
auth        required      pam_deny.so

account     required      pam_unix.so
account     sufficient    pam_localuser.so
account     sufficient    pam_succeed_if.so uid < 500 quiet
account     required      pam_permit.so

password    requisite     pam_cracklib.so try_first_pass retry=3
password    sufficient    pam_unix.so sha512 shadow nullok
try_first_pass use_authtok
password    required      pam_deny.so

session     optional      pam_keyinit.so revoke
session     required      pam_limits.so
session     [success=1 default=ignore] pam_succeed_if.so service in
crond quiet use_uid
session     required      pam_unix.so