This bug was fixed in the package libfprint -
1:1.90.7+git20210222+tod1-0ubuntu1
---------------
libfprint (1:1.90.7+git20210222+tod1-0ubuntu1) hirsute; urgency=medium
* New upstream TOD release
* Merge common packaging bits with debian
* debian/libfprint-2-2.postinst: Devices triggers updated
* debian/patches: Drop, they're all applied upstream
* debian/libfprint-2-2.symbols: Update symbols
* debian/update-udev-triggers.sh: Ignore udevadm trigger failures
(LP: #1909023)
* debian/libfprint-2-2.postinst: Regenerate as per generator changes
(LP: #1909023)
libfprint (1:1.90.7-3) experimental; urgency=medium
* gbp.conf: Prepare for experimental branching
* debian/patches:
- Use hwdb to store device autosuspend rules and drop debian specifics.
Upstream will use an hwdb to store the device autosuspend (that will be
included in systemd also, so libfprint packagin may stop shipping it at
later point), so use it earlier.
Drop the debian specific rules to set the devices part of the `plugdev`
group as such devices should not be ever readable by an user, but the
access should be managed through a libfprint-based service (frpintd at
the date).
- Explicitly mark libfprint as a shared library
* libfprint-2-2.install: Install hwdb file
* debian/rules:
- Do not autorename upstream rules file anymore.
It's not there, while there's no point to rename the hwdb one.
- Manually set udev hwdb directory (was rules dir before)
- Don't remove the meson generated private values from pc file.
This is now generated correctly by upstream, so no need to drop anything
from it.
* debian: Generate postinst devices list automatically at gbp import phase.
Alternatively provide a script to keep the post-inst script updated
* debian/libfprint-2-2.postinst: Upgrade as per upstream hwdb.
Blacklisted devices can be now removed from the trigger list as we don't
add them to plugdev anymore.
libfprint (1:1.90.7-2) unstable; urgency=medium
* debian/patches: Skip udev rules tests when not all drivers are compiled
* debian/libfprint-2-2.postinst: Regenerate the udev list based on new IDs
libfprint (1:1.90.7-1) unstable; urgency=medium
* New upstream release:
- vfs5011: Fix possible use-after-free
- goodixmoc: Add two new PIDs (0x63AC, 0x639C)
- goodixmoc: Support finger status API
- synaptics: Only identify within provided prints
- synaptics: Reject devices with old firmware during probe (#239)
* debian/patches:
- Refresh, dropping merged
- Include upstream udev fixes and use hardcoded rules
- Ensure that umockdev tests will pass with libusb 1.0.24
(Closes: #977848, #978256)
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Mon, 22 Feb 2021
21:39:04 +0100
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1909023
Title:
package libfprint-2-2:amd64 1:1.90.3+tod1-0ubuntu1 failed to
install/upgrade: installed libfprint-2-2:amd64 package post-
installation script subprocess returned error exit status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1909023/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
