[fprint] fprintd rejects sedond and other verify attempts

[Jaroslav Barton]

Dne Wednesday 18 February 2009 13:05:04 Jaroslav Barton napsal(a):
> Dne Wednesday 18 February 2009 11:44:19 Bastien Nocera napsal(a):
> > This means libfprint barfed on something the device did.
> >
> > You'll want to test with earlier kernel and see if that changes
> > anything. There was a bug in 2.6.28 kernels with USB devices which
> > caused problems with fingerprint software.
>
> Previous kernel verion I was using is 2.6.27.12-170.2.5.fc10 and fprintd
> works well.
>
> > Anything else, and fprint debug output will be needed.
>
> Hmm, I will do some tests.
>

Debug output:

$ ./enroll 
This program will enroll your right index finger, unconditionally overwriting 
any right-index 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 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] 0x1c609d0 entering state 0
drv:debug [__ssm_call_handler] 0x1c5f5f0 entering state 0
sync:debug [fp_enroll_finger_img] upekts will handle enroll stage 0/2
drv:debug [__ssm_call_handler] 0x1c5f5f0 entering state 1
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=2
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] 0x1c5f5f0 completed with status -1
drv:debug [fpi_ssm_mark_aborted] error -1 from state 0
drv:debug [fpi_ssm_mark_completed] 0x1c609d0 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] 0x1c609d0 entering state 0
upekts:debug [alloc_send_cmdresponse_transfer] seq=07 len=1
libusb:error [submit_bulk_transfer] submiturb failed error -1 errno=2
drv:debug [fpi_ssm_mark_aborted] error -1 from state 0
drv:debug [fpi_ssm_mark_completed] 0x1c609d0 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]

> Thanks

Thanks

-- 
Jaroslav Barton, Bc.
mail: djaara at djaara.net
jid : djaara at medoro.org
jid : djaara at njs.netlab.cz