This bug was fixed in the package fprintd - 1.90.9-1~ubuntu20.04.1
---------------
fprintd (1.90.9-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
fprintd (1.90.9-1) unstable; urgency=medium
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Fix multiple daemon lockup issues (#97)
- Fix print garbage collection to not delete used prints
- pam: Use the device with the most prints
* debian/control: Mark fprintd-doc as Multi-Arch: foreign
[ Helmut Grohne ]
* Fix nocheck FTFBS: Drop <!nocheck> from non-optional dependencies.
(Closes: #977395)
fprintd (1.90.8-1~ubuntu20.04.1) focal; urgency=medium
* Backport to focal (LP: #1908119)
* debian/{control,gbp.conf}: Prepare for ubuntu focal branching
* debian/{control, rules}: Do not use debhelper 13 features
* debian/rules: Use meson test directly to handle timeouts
* debian/patches: Drop all the patches applied upstream
fprintd (1.90.8-1) unstable; urgency=medium
* New upstream release
- pam: Only listen to NameOwnerChanged after fprintd is known to run
- Place new ObjectManager DBus API at /net/reactivated/Fprint
* debian/patches: Remove all patches, applied upstream or not needed anymore
* debian/control: Depend on systemd 235, but only in linux
* debian/rules: Require systemd and set unit path only on linux
* debian/fprintd.install: Use dh-exec to filter linux-only files
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
- Permit interactive authorization from fprintd utilities
- Do not allow deletion while another operation is ongoing
- pam: Guard strdup calls against NULL pointers
* debian/patches:
- Refresh
- Ignore NameOwnerChanged until fprintd is running
fprintd (1.90.5-2) unstable; urgency=medium
* debian/patches: Make tests run with actual required libfprint version
* debian/control: Remove test-only dependency on libfprint 1.90.4.
Tests are now working with older libfprint versions too
* debian/control: Add myself to Uploaders
* debian/gbp.conf: Include suggested settings by GNOME team.
Even if fprintd is not part of GNOME I think these settings are good
practice anyways.
fprintd (1.90.5-1) unstable; urgency=medium
* New upstream release:
- Permit building with polkit older than 0.114
- Fix possible issues with PAM test
- Fix incorrect DBus policy
- Fix build so that CFLAGS environment is correctly used
- Skip hotplug test with older libfprint (which times out otherwise)
* debian/patches: Drop patches applied upstream
fprintd (1.90.4-1) unstable; urgency=medium
* Team upload.
[ Marco Trevisan (Treviño) ]
* New upstream release:
- Use GDBus and async Polkit checks
- Authentication is now required to enroll a new print (LP: #1532264,
Closes: #719004)
- Add support for the libfprint early reporting mechanism
- Proper hotplug support together with libfprint 1.90.4
- Handle STATE_DIRECTORY containing multiple paths
- Various memory fixes (LP: #1888495)
* debian/control:
- Remove build dependency on dbus-glib (Closes: #955893)
- Mark as <!nocheck> the packages required only for testing
- Use debhelper 13
- Bump libfprint-2 dependency on 1.90.4 on test case
* debian/rules:
- remove unneeded override to force --fail-missing (as per dh 13)
- Increase tests timeout multiplier
* debian/patches:
- Refresh
- Define auto-pointers functions if not defined:
Fixes a build failure with debian polkit version.
- Cleanup pam-wrapper temporary dir when running tests
- Fix dbus-policy file to address lintian
- Ensure we generate debug symbols in debian builds
[ Laurent Bigonville ]
* debian/control: Bump Standards-Version to 4.5.1 (no further changes)
fprintd (1.90.1-2) unstable; urgency=low
* Team upload.
* Simplify the installation of the pam-config, do not install one
configuration file per architecture
* debian/NEWS: Add an news entry explaining that the user will have to
re-enroll their fingerprints upon update to 1.90.1.
-- Marco Trevisan (Treviño) <[email protected]> Mon, 22 Feb 2021
16:00:47 +0100
** Changed in: fprintd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fprintd in Ubuntu.
https://bugs.launchpad.net/bugs/1888495
Title:
fprintd-verify fails with an USB UPEK reader
Status in fprintd package in Ubuntu:
Fix Released
Status in libfprint package in Ubuntu:
Triaged
Status in fprintd source package in Focal:
Fix Released
Status in fprintd source package in Groovy:
Fix Committed
Bug description:
[ Impact ]
The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It
was working fine with ubuntu 16.04 and 18.04.
[ Test case ]
With an UPEK fingerprint reader run:
- fprintd-verify
Verification should work properly
[ Regression potential ]
Fingers are not verified
----
lsusb shows:
0483:2016 STMicroelectronics Fingerprint Reader
user@xubuntu:~$ fprintd-enroll
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Open failed with error: transfer timed out
user@xubuntu:~$ fprintd-list user
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
User user has no fingers enrolled for UPEK TouchStrip.
This bug is probably the same as:
https://bugzilla.redhat.com/show_bug.cgi?id=1832229
Related to bug #1881380
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1888495/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
