ewanm89 wrote:
> On Sat, 27 Dec 2008 01:35:29 +0200
> Alon Bar-Lev <[email protected]> wrote:
>
>> Here is the debug log.
>>
>> Ends up with Enroll failed with error -22.
>>
>> Thanks!
>>
>> $ pam_fprint_enroll
>> This program will enroll your finger, unconditionally overwriting any
>> selected print that was enrolled previously. If you want to continue,
>> press enter, otherwise hit Ctrl+C
>>
>> fp:debug [fp_init]
>> fp:debug [register_driver] registered driver upekts
>> fp:debug [register_driver] registered driver aes4000
>> fp:debug [register_driver] registered driver aes2501
>> fp:debug [register_driver] registered driver uru4000
>> fp:debug [register_driver] registered driver vcom5s
>> fp:debug [register_driver] registered driver upeksonly
>> fp:debug [find_supporting_driver] driver upekts supports USB device
>> 0483:2016 Found device claimed by UPEK TouchStrip driver
>> sync:debug [fp_dev_open]
>> async:debug [fp_async_dev_open]
>> async:debug [fpi_drvcb_open_complete] status 0
>> sync:debug [sync_open_cb] status 0
>> Opened device. It's now time to enroll your finger.
>>
>> You will need to successfully scan your Right Index Finger 3 times to
>> complete the process.
>>
>> Scan your finger now.
>> sync:debug [fp_enroll_finger_img]
>> async:debug [fp_async_enroll_start] starting enrollment
>> drv:debug [__ssm_call_handler] 0x8e02270 entering state 0
>> drv:debug [__ssm_call_handler] 0x8e02298 entering state 0
>> sync:debug [fp_enroll_finger_img] upekts will handle enroll stage 0/2
>> drv:debug [__ssm_call_handler] 0x8e02298 entering state 1
>> upekts:error [initsm_read_msg_handler] async read msg failed in state
>> 1 drv:debug [fpi_ssm_mark_aborted] error -1 from state 1
>> drv:debug [fpi_ssm_mark_completed] 0x8e02298 completed with status -1
>> drv:debug [fpi_ssm_mark_aborted] error -1 from state 0
>> drv:debug [fpi_ssm_mark_completed] 0x8e02270 completed with status -1
>> async:debug [fpi_drvcb_enroll_started] status -1
>> sync:debug [sync_enroll_cb] result -1
>> sync:error [fp_enroll_finger_img] unrecognised return code -1
>> sync:debug [fp_enroll_finger_img] ending enrollment
>> async:debug [fp_async_enroll_stop]
>> drv:debug [__ssm_call_handler] 0x8e02270 entering state 0
>> upekts:debug [alloc_send_cmdresponse_transfer] seq=07 len=1
>> drv:debug [fpi_ssm_mark_aborted] error -1 from state 0
>> drv:debug [fpi_ssm_mark_completed] 0x8e02270 completed with status -1
>> async:debug [fpi_drvcb_enroll_stopped]
>> sync:debug [enroll_stop_cb]
>> Enroll failed with error -22
>> sync:debug [fp_dev_close]
>> async:debug [fpi_drvcb_close_complete]
>> sync:debug [sync_close_cb]
>> fp:debug [fp_exit]
>> _______________________________________________
>> fprint mailing list
>> [email protected]
>> http://lists.reactivated.net/mailman/listinfo/fprint
>
> Don't know whether it is related but I use pam_fprint and it grabs the
> print and verifies it all fine the first time scan is required but the
> next time it just hangs waiting for a print.
Ack, i have that regression with 2.6.28 too. Just turned pam_fprint off
for now, if any of the devs want straces/debug logs, please ask me.
Christian
_______________________________________________
fprint mailing list
[email protected]
http://lists.reactivated.net/mailman/listinfo/fprint
