** Changed in: libfprint-2-tod1-goodix
Status: Fix Committed => Fix Released
--
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/1966911
Title:
Cannot enroll finger on Jammy
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
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/1966911
Title:
Cannot enroll finger on Jammy
Status in
This bug was fixed in the package libfprint -
1:1.94.3+tod1-0ubuntu2~22.04.01
---
libfprint (1:1.94.3+tod1-0ubuntu2~22.04.01) jammy; urgency=medium
* debian/patches: Ensure that identify works with old goodix driver
(LP: #1966911)
* debian: Update references to jammy branch
** Changed in: libfprint (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: libfprint (Ubuntu Jammy)
Milestone: None => ubuntu-22.04.1
** Changed in: libfprint (Ubuntu)
Milestone: ubuntu-22.04.1 => None
** Changed in: fprintd (Ubuntu)
Milestone: ubuntu-22.04.1 => None
** Changed in: fprintd (Ubuntu Jammy)
Status: New => Invalid
** Changed in: libfprint (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: libfprint (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: libfprint (Ubuntu Jammy)
Assignee: (unassigned) => Marco
As this SRU touches existing code, I would like to see a regression
potential section added to the bug description [1], aka. "Where problems
could occur". Can someone take a look and write up some ideas on what
could go wrong in case the cherry-picked code is buggy? Thanks.
[1]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2
---
libfprint (1:1.94.3+tod1-0ubuntu2) kinetic; urgency=medium
* debian/patches: Ensure that identify works with old goodix driver
(LP: #1966911)
-- Marco Trevisan (Treviño) Sun, 17 Jul 2022
17:37:33 +0200
** Changed in: libfprint-2-tod1-goodix
Status: Invalid => Fix Committed
** Changed in: libfprint (Ubuntu)
Status: Won't Fix => Fix Committed
** Changed in: fprintd (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of
So, apparently libfprint is still working fine, as I can properly run
the libfprint's examples to enroll, identify and verify the prints.
While fprintd seems to handle this poorly.
** Changed in: libfprint-2-tod1-goodix
Status: Confirmed => Invalid
** Changed in: libfprint (Ubuntu)
9 matches
Mail list logo