Andy mentioned that he is having a Broadcom CV enabled laptop, it would be
good for you to have one laptop for testing purposes.
Yes, as you mentioned, the log didn't have any errors and I was not sure
why the login screen was unlocked.
Thanks,
Prafulla
On Mon, Jul 18, 2022 at 8:41 PM Marco Trevisan (Treviño) <
<email address hidden>> wrote:
> Mh, I don't see traces of failures there.
>
> I can't debug it easily without hw, but maybe is it hanging?
> Can you provide a gdb backtrace for all the threads?
>
> --
> 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
>
> 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
>
>
Hi Marco,
Andy mentioned that he is having a Broadcom CV enabled laptop, it would be
good for you to have one laptop for testing purposes.
Yes, as you mentioned, the log didn't have any errors and I was not sure
why the login screen was unlocked.
Thanks,
Prafulla
On Mon, Jul 18, 2022 at 8:41 PM Marco Trevisan (Treviño) <
<email address hidden>> wrote:
> Mh, I don't see traces of failures there. /bugs.launchpad .net/bugs/ 1981974 2-tod1- broadcom: /bugs.launchpad .net/libfprint- 2-tod1- broadcom/ +bug/1981974/ +subscriptions
>
> I can't debug it easily without hw, but maybe is it hanging?
> Can you provide a gdb backtrace for all the threads?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> FP identify is not working with broadcom sensor on Jammy
>
> Status in libfprint-
> 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:/
>
>
--
Thanks,
Prafulla Kota
9866544810