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)
Status: Confirmed => Won't Fix
** Also affects: fprintd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: fprintd (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: fprintd (Ubuntu)
Milestone: None => ubuntu-22.04.1
** Changed in: fprintd (Ubuntu)
Status: New => Triaged
--
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 libfprint-2-tod1-goodix:
Invalid
Status in OEM Priority Project:
Confirmed
Status in fprintd package in Ubuntu:
Triaged
Status in libfprint package in Ubuntu:
Won't Fix
Bug description:
[Summary]
Cannot enroll finger on Jammy.
[Steps]
1. Install Jammy on XPS-9310
2. Open Gnome-control-center and select `User`
3. Enroll fingerprint
[Expected]
Enroll fingerprint without issue.
[Actual]
Cannot enroll fingerprint
To manage notifications about this bug go to:
https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+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
