Sorry for the delay, the log is apprarently similar.
(fprintd:35181): fprintd-DEBUG: 17:52:41.283: claimed device 0 (fprintd:35181): fprintd-DEBUG: 17:52:41.287: file_storage_discover_prints() for user 'ark' in '/var/lib/fprint/ark/upekts/0' (fprintd:35181): fprintd-DEBUG: 17:52:41.287: start verification device 0 finger 7 (fprintd:35181): fprintd-DEBUG: 17:52:41.287: file_storage_print_data_load(): loaded '/var/lib/fprint/ark/upekts/0/7' Success (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.287: [upekts] VERIFY_NUM_STATES entering state 0 (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.287: [upekts] INITSM_NUM_STATES entering state 0 (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.288: [upekts] INITSM_NUM_STATES entering state 1 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.289: A=03 B=00 len=5 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.289: cmd 3 from device to driver (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.289: [upekts] INITSM_NUM_STATES entering state 2 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.289: seq=04 len=8 (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.290: [upekts] INITSM_NUM_STATES entering state 3 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.291: A=05 B=00 len=1 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.291: cmd 5 from device to driver (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.291: [upekts] INITSM_NUM_STATES entering state 4 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.291: seq=00 subcmd=06 with 1 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.292: [upekts] INITSM_NUM_STATES entering state 5 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.297: A=00 B=00 len=55 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.297: device responds to subcmd 6 with 49 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.297: [upekts] INITSM_NUM_STATES entering state 6 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.297: seq=10 subcmd=07 with 1 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.298: [upekts] INITSM_NUM_STATES entering state 7 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.299: A=00 B=10 len=15 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.299: device responds to subcmd 7 with 9 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.299: [upekts] INITSM_NUM_STATES entering state 8 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.299: seq=20 subcmd=08 with 25 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.300: [upekts] INITSM_NUM_STATES entering state 9 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.303: A=00 B=20 len=15 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.303: device responds to subcmd 8 with 9 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.303: [upekts] INITSM_NUM_STATES entering state 10 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.303: seq=30 subcmd=0c with 5 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.304: [upekts] INITSM_NUM_STATES entering state 11 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.304: didn't fit in buffer, need to extend by 52 bytes (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.305: A=00 B=30 len=107 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.305: device responds to subcmd c with 101 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.305: [upekts] INITSM_NUM_STATES entering state 12 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.305: seq=40 subcmd=0b with 105 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.306: [upekts] INITSM_NUM_STATES entering state 13 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.307: A=00 B=40 len=7 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.307: device responds to subcmd b with 1 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.307: [upekts] INITSM_NUM_STATES completed successfully (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.307: [upekts] VERIFY_NUM_STATES entering state 1 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.307: seq=50 subcmd=03 with 164 bytes of data (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.308: [upekts] VERIFY_NUM_STATES completed successfully (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.309: A=00 B=50 len=7 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.309: non-zero bytes in cmd response (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.309: device responds to subcmd f0 with 1 bytes (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.309: [upekts] DEINITSM_NUM_STATES entering state 0 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.309: seq=07 len=1 (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.310: [upekts] DEINITSM_NUM_STATES entering state 1 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.311: A=01 B=00 len=0 (fprintd:35181): libfprint-upekts-DEBUG: 17:52:41.311: cmd 1 from device to driver (fprintd:35181): libfprint-SSM-DEBUG: 17:52:41.311: [upekts] DEINITSM_NUM_STATES completed successfully (fprintd:35181): libfprint-device-DEBUG: 17:52:41.311: Device reported verify completion (fprintd:35181): libfprint-device-DEBUG: 17:52:41.311: Completing action 5 in idle! (fprintd:35181): fprintd-DEBUG: 17:52:41.311: verify_cb: result verify-disconnect
(fprintd:35181): fprintd-WARNING **: 17:52:41.311: Device reported an error during verify: Response had wrong subcommand type (fprintd:35181): libfprint-device-DEBUG: 17:52:41.317: Device reported close completion (fprintd:35181): libfprint-device-DEBUG: 17:52:41.317: Completing action 3 in idle! (fprintd:35181): fprintd-DEBUG: 17:52:41.317: released device 0
Sorry for the delay, the log is apprarently similar.
(fprintd:35181): fprintd-DEBUG: 17:52:41.283: claimed device 0 discover_ prints( ) for user 'ark' in '/var/lib/ fprint/ ark/upekts/ 0' print_data_ load(): loaded '/var/lib/ fprint/ ark/upekts/ 0/7' Success SSM-DEBUG: 17:52:41.287: [upekts] VERIFY_NUM_STATES entering state 0 SSM-DEBUG: 17:52:41.287: [upekts] INITSM_NUM_STATES entering state 0 SSM-DEBUG: 17:52:41.288: [upekts] INITSM_NUM_STATES entering state 1 upekts- DEBUG: 17:52:41.289: A=03 B=00 len=5 upekts- DEBUG: 17:52:41.289: cmd 3 from device to driver SSM-DEBUG: 17:52:41.289: [upekts] INITSM_NUM_STATES entering state 2 upekts- DEBUG: 17:52:41.289: seq=04 len=8 SSM-DEBUG: 17:52:41.290: [upekts] INITSM_NUM_STATES entering state 3 upekts- DEBUG: 17:52:41.291: A=05 B=00 len=1 upekts- DEBUG: 17:52:41.291: cmd 5 from device to driver SSM-DEBUG: 17:52:41.291: [upekts] INITSM_NUM_STATES entering state 4 upekts- DEBUG: 17:52:41.291: seq=00 subcmd=06 with 1 bytes of data SSM-DEBUG: 17:52:41.292: [upekts] INITSM_NUM_STATES entering state 5 upekts- DEBUG: 17:52:41.297: A=00 B=00 len=55 upekts- DEBUG: 17:52:41.297: device responds to subcmd 6 with 49 bytes SSM-DEBUG: 17:52:41.297: [upekts] INITSM_NUM_STATES entering state 6 upekts- DEBUG: 17:52:41.297: seq=10 subcmd=07 with 1 bytes of data SSM-DEBUG: 17:52:41.298: [upekts] INITSM_NUM_STATES entering state 7 upekts- DEBUG: 17:52:41.299: A=00 B=10 len=15 upekts- DEBUG: 17:52:41.299: device responds to subcmd 7 with 9 bytes SSM-DEBUG: 17:52:41.299: [upekts] INITSM_NUM_STATES entering state 8 upekts- DEBUG: 17:52:41.299: seq=20 subcmd=08 with 25 bytes of data SSM-DEBUG: 17:52:41.300: [upekts] INITSM_NUM_STATES entering state 9 upekts- DEBUG: 17:52:41.303: A=00 B=20 len=15 upekts- DEBUG: 17:52:41.303: device responds to subcmd 8 with 9 bytes SSM-DEBUG: 17:52:41.303: [upekts] INITSM_NUM_STATES entering state 10 upekts- DEBUG: 17:52:41.303: seq=30 subcmd=0c with 5 bytes of data SSM-DEBUG: 17:52:41.304: [upekts] INITSM_NUM_STATES entering state 11 upekts- DEBUG: 17:52:41.304: didn't fit in buffer, need to extend by 52 bytes upekts- DEBUG: 17:52:41.305: A=00 B=30 len=107 upekts- DEBUG: 17:52:41.305: device responds to subcmd c with 101 bytes SSM-DEBUG: 17:52:41.305: [upekts] INITSM_NUM_STATES entering state 12 upekts- DEBUG: 17:52:41.305: seq=40 subcmd=0b with 105 bytes of data SSM-DEBUG: 17:52:41.306: [upekts] INITSM_NUM_STATES entering state 13 upekts- DEBUG: 17:52:41.307: A=00 B=40 len=7 upekts- DEBUG: 17:52:41.307: device responds to subcmd b with 1 bytes SSM-DEBUG: 17:52:41.307: [upekts] INITSM_NUM_STATES completed successfully SSM-DEBUG: 17:52:41.307: [upekts] VERIFY_NUM_STATES entering state 1 upekts- DEBUG: 17:52:41.307: seq=50 subcmd=03 with 164 bytes of data SSM-DEBUG: 17:52:41.308: [upekts] VERIFY_NUM_STATES completed successfully upekts- DEBUG: 17:52:41.309: A=00 B=50 len=7 upekts- DEBUG: 17:52:41.309: non-zero bytes in cmd response upekts- DEBUG: 17:52:41.309: device responds to subcmd f0 with 1 bytes SSM-DEBUG: 17:52:41.309: [upekts] DEINITSM_NUM_STATES entering state 0 upekts- DEBUG: 17:52:41.309: seq=07 len=1 SSM-DEBUG: 17:52:41.310: [upekts] DEINITSM_NUM_STATES entering state 1 upekts- DEBUG: 17:52:41.311: A=01 B=00 len=0 upekts- DEBUG: 17:52:41.311: cmd 1 from device to driver SSM-DEBUG: 17:52:41.311: [upekts] DEINITSM_NUM_STATES completed successfully device- DEBUG: 17:52:41.311: Device reported verify completion device- DEBUG: 17:52:41.311: Completing action 5 in idle!
(fprintd:35181): fprintd-DEBUG: 17:52:41.287: file_storage_
(fprintd:35181): fprintd-DEBUG: 17:52:41.287: start verification device 0 finger 7
(fprintd:35181): fprintd-DEBUG: 17:52:41.287: file_storage_
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): fprintd-DEBUG: 17:52:41.311: verify_cb: result verify-disconnect
(fprintd:35181): fprintd-WARNING **: 17:52:41.311: Device reported an error during verify: Response had wrong subcommand type device- DEBUG: 17:52:41.317: Device reported close completion device- DEBUG: 17:52:41.317: Completing action 3 in idle!
(fprintd:35181): libfprint-
(fprintd:35181): libfprint-
(fprintd:35181): fprintd-DEBUG: 17:52:41.317: released device 0