Give immediately up with no camera

[GoogleCodeExporter]

This would be useful for users that don't always have the webcam connected,
who have it set up to bypass password authentication (with "sufficient" at
the beginning of the pam file).

When some action (e.g. logging in) is set up to use pam-face-authentication
but there is no webcam connected it still waits for a certain ammount of
time before giving up and letting the user enter a password.

It would be nice if it gave up more immediately, not forcing the user to
wait before entering a password.

Also, congratulations - everything works on ArchLinux with the Slim login
manager.

Original issue reported on code.google.com by yuriy.sv...@gmail.com on 24 Apr 2010 at 9:05

[GoogleCodeExporter]

:-/ it should have said "Give up immediately"
Also it should be an enhancement.

Original comment by yuriy.sv...@gmail.com on 24 Apr 2010 at 9:07

[GoogleCodeExporter]

Noted. I will fix this in the next release :) 

Thanks

Original comment by rohan.a...@gmail.com on 30 Apr 2010 at 9:30

• Changed state: Started
• Added labels: Type-Enhancement, Usability
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thanks for responding so quickly.

Also this might help:
I noticed that it only happens when other USB devices are plugged in (when 
nothing is
plugged in it gives up immediately).

Original comment by yuriy.sv...@gmail.com on 23 May 2010 at 5:03

[GoogleCodeExporter]

are you sure about this. I will need your help debugging this. Code is written 
to
exit immediately if webcam is not found.

Original comment by rohan.a...@gmail.com on 24 May 2010 at 7:46

[GoogleCodeExporter]

I just tried a couple of different things and noticed this:

If I have any USB device plugged in, Slim, the login manager, hangs for a 
minute as 
if it's trying to authenticate with the (absent) webcam.
When I look at the log it just has the webcam-not-found message.

Moreover, when I try to use the authentication with su, it immediately tells me 
there 
is no webcam and exits (no wait).

If I remember right xscreensaver behaved like slim as well.

I don't know, do you think it might just be something specific to my setup?
Do you know of any possible reason why it would wait in one case but not 
another?

Original comment by yuriy.sv...@gmail.com on 25 May 2010 at 5:28

[GoogleCodeExporter]

you could attach gdb to slim 
gdb ( attach PID )
and when its stuck in some processing
Ctrl + C and look at bt
Look at which function is being executed 

http://code.google.com/p/pam-face-authentication/source/browse/trunk/qtbranch/sr
c/pam_face_authentication.cpp
look at #423
    if (webcam.startCamera()==0)
then exit

Original comment by rohan.a...@gmail.com on 25 May 2010 at 6:30

[GoogleCodeExporter]

I have also added an option in one XML file which would allow the root to set 
the
timeout ( that is for how much time it should try recognizing the face ).

I will release 0.4 version this week, Mostly usability improvements.

Original comment by rohan.a...@gmail.com on 25 May 2010 at 6:32