Hi Andy,

I verified with 2 fingers and observed that both Fingers Identity is
working fine, let me know if i need to provide any other info, it is not
working with single FP identify  template on 22.04.
Does anything need to be changed from tod driver to support this feature on
22.04?

fprintd-verify is returning an error even with 2 fingers enrolled, but the
Login screen is successful with 2 finger enrollment.

if you can help to change my email for bug communication, can you add my
official email id:  "<email address hidden>" to this list, as i was
suggested to use this e-mail for communication, i did change  e-mail at my
profile, but this issue was created before it got changed.

fprintd-verify application log posted below: fprintd claiming FP verify is
failed, but login screen FP identify is working good.

(fprintd:3334): libfprint-device-DEBUG: 16:26:41.665: Completing action
FPI_DEVICE_ACTION_PROBE in idle!
(fprintd:3334): libfprint-device-DEBUG: 16:26:41.665: Updated temperature
model after 0.21 seconds, ratio 0.27 -> 0.27, active 0 -> 0,
FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(fprintd:3334): fprintd-DEBUG: 16:26:41.668: Device Broadcom Sensors scan
type changed to 'press'
(fprintd:3334): fprintd-DEBUG: 16:26:41.668: Device Broadcom Sensors enroll
stages changed to 11
(fprintd:3334): fprintd-DEBUG: 16:26:41.668: Finger present 0
(fprintd:3334): fprintd-DEBUG: 16:26:41.668: Finger needed 0
(fprintd:3334): fprintd-DEBUG: 16:26:41.669: entering main loop
(fprintd:3334): fprintd-DEBUG: 16:26:41.669: D-Bus service launched with
name: net.reactivated.Fprint
(fprintd:3334): fprintd-DEBUG: 16:26:55.513: Requesting authorization from
:1.148 to call method 'Claim' for device 'Broadcom Sensors'
(fprintd:3334): fprintd-DEBUG: 16:26:55.514: Getting authorization to
perform Polkit action net.reactivated.fprint.device.verify
(fprintd:3334): fprintd-DEBUG: 16:26:55.521: Authorization granted to
:1.148 to call method 'Claim' for device 'Broadcom Sensors'!
(fprintd:3334): fprintd-DEBUG: 16:26:55.521: user 'adminuser' claiming the
device: 0
(fprintd:3334): libfprint-device-DEBUG: 16:26:55.636: Device reported open
completion
(fprintd:3334): libfprint-device-DEBUG: 16:26:55.637: Completing action
FPI_DEVICE_ACTION_OPEN in idle!
(fprintd:3334): libfprint-device-DEBUG: 16:26:55.637: Updated temperature
model after 13.97 seconds, ratio 0.27 -> 0.26, active 0 -> 0,
FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
(fprintd:3334): fprintd-DEBUG: 16:26:55.637: claimed device 0
(fprintd:3334): fprintd-DEBUG: 16:26:55.639: Requesting authorization from
:1.148 to call method 'ListEnrolledFingers' for device 'Broadcom Sensors'
(fprintd:3334): fprintd-DEBUG: 16:26:55.640: Getting authorization to
perform Polkit action net.reactivated.fprint.device.verify
(fprintd:3334): fprintd-DEBUG: 16:26:55.646: Authorization granted to
:1.148 to call method 'ListEnrolledFingers' for device 'Broadcom Sensors'!
(fprintd:3334): fprintd-DEBUG: 16:26:55.646: file_storage_discover_prints()
for user 'adminuser' in '/var/lib/fprint/adminuser/broadcom/0'
(fprintd:3334): fprintd-DEBUG: 16:26:55.646:
file_storage_print_data_load(): loaded
'/var/lib/fprint/adminuser/broadcom/0/a' Success
(fprintd:3334): fprintd-DEBUG: 16:26:55.646:
file_storage_print_data_load(): loaded
'/var/lib/fprint/adminuser/broadcom/0/2' Success
(fprintd:3334): fprintd-DEBUG: 16:26:55.648: Requesting authorization from
:1.148 to call method 'VerifyStart' for device 'Broadcom Sensors'
(fprintd:3334): fprintd-DEBUG: 16:26:55.648: Getting authorization to
perform Polkit action net.reactivated.fprint.device.verify
(fprintd:3334): fprintd-DEBUG: 16:26:55.652: Authorization granted to
:1.148 to call method 'VerifyStart' for device 'Broadcom Sensors'!
(fprintd:3334): fprintd-DEBUG: 16:26:55.652:
file_storage_print_data_load(): loaded
'/var/lib/fprint/adminuser/broadcom/0/a' Success
(fprintd:3334): fprintd-DEBUG: 16:26:55.652: start verification device 0
finger right-little-finger
(fprintd:3334): libfprint-device-DEBUG: 16:26:55.652: Updated temperature
model after 0.02 seconds, ratio 0.26 -> 0.26, active 1 -> 1,
FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
** (fprintd:3334): DEBUG: 16:26:55.652: data is 0x7f4024009b00
** (fprintd:3334): DEBUG: 16:26:55.652: user_id:
FP1-20220811-A-07698023-adminuser, finger: 10
** (fprintd:3334): DEBUG: 16:26:55.652: templateHandle is 7698023
Capture Initiated, Please place your finger now on the sensor now
The interrupt processed data 3
** (fprintd:3334): DEBUG: 16:26:57.714: Verify failed!

(fprintd:3334): libfprint-device-DEBUG: 16:26:57.714: Device reported
verify result
(fprintd:3334): fprintd-DEBUG: 16:26:57.714: report_verify_status: result
verify-no-match
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Device reported
verify completion
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Updated temperature
model after 2.06 seconds, ratio 0.26 -> 0.27, active 1 -> 1,
FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Completing action
FPI_DEVICE_ACTION_VERIFY in idle!
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Updated temperature
model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0,
FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
(fprintd:3334): fprintd-DEBUG: 16:26:57.715: verify_cb: result
verify-no-match
(fprintd:3334): fprintd-DEBUG: 16:26:57.715: Device Broadcom Sensors failed
to match during action 2, verifying local storage
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Device reported
listing completion

(fprintd:3334): libfprint-device-WARNING **: 16:26:57.715: Driver did not
pass array but failed to provide an error
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Completing action
FPI_DEVICE_ACTION_LIST in idle!
(fprintd:3334): libfprint-device-DEBUG: 16:26:57.715: Updated temperature
model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0,
FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM

(fprintd:3334): fprintd-WARNING **: 16:26:57.715: Failed to query prints:
Driver failed to provide a list of prints
(fprintd:3334): libfprint-device-DEBUG: 16:27:00.686: Updated temperature
model after 2.97 seconds, ratio 0.27 -> 0.27, active 0 -> 0,
FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD




Thanks,
Prafulla

On Thu, Aug 11, 2022 at 3:46 PM Andy Chi <email address hidden> wrote:

> Enrolled second finger on DUT and I can login without problem.
> @prafullakota, can you help to check on your side?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1981974
>
> Title:
>   FP identify is not working with broadcom sensor on Jammy
>
> Status in libfprint-2-tod1-broadcom:
>   New
> Status in libfprint package in Ubuntu:
>   New
>
> Bug description:
>   Broadcom Jammy package is provided to canonical team (Andy), attached
>   the log file shows FP identify operation says that verification is
>   successful, but Login screen will NOT be unlocked.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1981974/+subscriptions
>
>

-- 
Thanks,
Prafulla Kota
9866544810