[Desktop-packages] [Bug 1956885] Re: Incorrect verify implementation, unable to verify on one finger
Hi Loic, I built a new deb here, please also check on your side. I can verify with one finger. fpritd-verify also works from my testing. https://launchpad.net/~andch/+archive/ubuntu/staging-fprint ** No longer affects: libfprint (Ubuntu) ** Changed in: oem-priority Status: Confirmed => In Progress ** Changed in: libfprint-2-tod1-broadcom Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1956885 Title: Incorrect verify implementation, unable to verify on one finger Status in libfprint-2-tod1-broadcom: In Progress Status in OEM Priority Project: In Progress Bug 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. Duplicate bug #1981974 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956885] Re: Incorrect verify implementation, unable to verify on one finger
** Changed in: libfprint-2-tod1-broadcom Status: New => Confirmed ** Changed in: libfprint-2-tod1-broadcom Importance: Undecided => Critical ** Changed in: libfprint-2-tod1-broadcom Assignee: (unassigned) => Andy Chi (andch) ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1985872 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1956885 Title: Incorrect verify implementation, unable to verify on one finger Status in libfprint-2-tod1-broadcom: Confirmed Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Confirmed Bug 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. Duplicate bug #1981974 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
