| 2022-01-09 21:27:31 |
Loic Yhuel |
bug |
|
|
added bug |
| 2022-01-09 21:31:25 |
Loic Yhuel |
description |
The closed-source library blocks on synchronous USB transfers in its "verify" method (at least, there might be others with the same issue).
The "identify" one is correct (asynchronous).
As a result :
$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
(finger pressed)
Verify started!
Verifying: right-index-finger
(blocked)
"Verify started!" should happen immediately, but the code libfprint code waits for fp_device_verify to return, which only happens when the finger is pressed with this driver.
The verify success message is sent during the call, so it is ignored.
"fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work correctly.
But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 (so I suppose on jammy), the "verify" method will be used instead if only one finger is enrolled.
TL,DR: the fingerprint reader appears to mostly work on focal, but starting with jammy it won't unless at least two fingers are enrolled. |
The closed-source library blocks on synchronous USB transfers in its "verify" method (at least, there might be others with the same issue).
The "identify" one is correct (asynchronous).
As a result :
$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
(finger pressed)
Verify started!
Verifying: right-index-finger
(blocked)
"Verify started!" should happen immediately, but the code libfprint code waits for fp_device_verify to return, which only happens when the finger is pressed with this driver.
The verify success message is sent during the call, so it is ignored.
"fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work correctly.
But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 (so I suppose on jammy), the "verify" method will be used instead if only one finger is enrolled.
TL,DR: the fingerprint reader appears to mostly work on focal, but starting with jammy it won't unless at least two fingers are enrolled.
Note that this is tested on a Dell Latitude 5521, but the issue should be the same with all Broadcom fingerprint readers using this library. |
|
| 2022-08-11 09:27:48 |
Andy Chi |
summary |
Incorrect verify implementation, unable to verify one one finger |
Incorrect verify implementation, unable to verify on one finger |
|
| 2022-08-15 14:17:10 |
Andy Chi |
libfprint-2-tod1-broadcom: status |
New |
Confirmed |
|
| 2022-08-15 14:17:11 |
Andy Chi |
libfprint-2-tod1-broadcom: importance |
Undecided |
Critical |
|
| 2022-08-15 14:17:14 |
Andy Chi |
libfprint-2-tod1-broadcom: assignee |
|
Andy Chi (andch) |
|
| 2022-08-15 14:17:27 |
Andy Chi |
bug task added |
|
libfprint (Ubuntu) |
|
| 2022-08-15 14:20:23 |
Andy Chi |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
| 2022-08-15 14:20:27 |
Andy Chi |
tags |
|
oem-priority originate-from-1985872 somerville |
|
| 2022-08-15 14:21:20 |
Andy Chi |
bug |
|
|
added subscriber Marco Trevisan (Treviño) |
| 2022-08-15 14:21:47 |
Andy Chi |
bug |
|
|
added subscriber sheldonwang |
| 2022-08-15 14:22:32 |
Andy Chi |
bug |
|
|
added subscriber prafulla chandra kota |
| 2022-08-15 14:22:58 |
Launchpad Janitor |
libfprint (Ubuntu): status |
New |
Confirmed |
|
| 2022-08-15 14:23:22 |
Andy Chi |
description |
The closed-source library blocks on synchronous USB transfers in its "verify" method (at least, there might be others with the same issue).
The "identify" one is correct (asynchronous).
As a result :
$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
(finger pressed)
Verify started!
Verifying: right-index-finger
(blocked)
"Verify started!" should happen immediately, but the code libfprint code waits for fp_device_verify to return, which only happens when the finger is pressed with this driver.
The verify success message is sent during the call, so it is ignored.
"fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work correctly.
But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 (so I suppose on jammy), the "verify" method will be used instead if only one finger is enrolled.
TL,DR: the fingerprint reader appears to mostly work on focal, but starting with jammy it won't unless at least two fingers are enrolled.
Note that this is tested on a Dell Latitude 5521, but the issue should be the same with all Broadcom fingerprint readers using this library. |
The closed-source library blocks on synchronous USB transfers in its "verify" method (at least, there might be others with the same issue).
The "identify" one is correct (asynchronous).
As a result :
$ fprintd-verify
Using device /net/reactivated/Fprint/Device/0
Listing enrolled fingers:
- #0: right-index-finger
(finger pressed)
Verify started!
Verifying: right-index-finger
(blocked)
"Verify started!" should happen immediately, but the code libfprint code waits for fp_device_verify to return, which only happens when the finger is pressed with this driver.
The verify success message is sent during the call, so it is ignored.
"fprintd-verify -f any" and pam-fprintd use fp_device_identify, so they work correctly.
But with https://gitlab.freedesktop.org/libfprint/fprintd/-/commit/fc65055279 (so I suppose on jammy), the "verify" method will be used instead if only one finger is enrolled.
TL,DR: the fingerprint reader appears to mostly work on focal, but starting with jammy it won't unless at least two fingers are enrolled.
Note that this is tested on a Dell Latitude 5521, but the issue should be the same with all Broadcom fingerprint readers using this library.
Duplicate bug #1981974 |
|
| 2022-08-15 14:53:53 |
Andy Chi |
oem-priority: assignee |
|
Andy Chi (andch) |
|
| 2022-08-15 14:53:55 |
Andy Chi |
oem-priority: importance |
Undecided |
Critical |
|
| 2022-08-15 14:53:58 |
Andy Chi |
oem-priority: status |
New |
Confirmed |
|
| 2022-08-22 13:53:13 |
prafulla chandra kota |
attachment added |
|
verify_left_singleFP_COMP_identify_two_finger.html https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+attachment/5610747/+files/verify_left_singleFP_COMP_identify_two_finger.html |
|
| 2022-08-22 14:46:27 |
Jay Chen |
bug |
|
|
added subscriber Jay Chen |
| 2022-08-23 10:26:47 |
prafulla chandra kota |
attachment added |
|
verify_linux.txt https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+attachment/5610964/+files/verify_linux.txt |
|
| 2022-09-09 21:38:15 |
Slavik Birger |
bug |
|
|
added subscriber Paul Munguia |
| 2022-09-14 06:05:32 |
Andy Chi |
bug task deleted |
libfprint (Ubuntu) |
|
|
| 2022-09-14 06:05:48 |
Andy Chi |
oem-priority: status |
Confirmed |
In Progress |
|
| 2022-09-14 06:05:49 |
Andy Chi |
libfprint-2-tod1-broadcom: status |
Confirmed |
In Progress |
|
| 2022-09-16 05:12:48 |
prafulla chandra kota |
bug |
|
|
added subscriber Slavik Birger |
| 2022-10-04 07:38:21 |
sheldonwang |
removed subscriber sheldonwang |
|
|
|
| 2022-10-25 07:21:02 |
Andy Chi |
oem-priority: status |
In Progress |
Triaged |
|
| 2022-10-25 07:21:05 |
Andy Chi |
libfprint-2-tod1-broadcom: status |
In Progress |
Triaged |
|
