Device using vfs301 driver crashes during verification
Bug #1905597 reported by
Marco Trevisan (Treviño)
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libfprint (Ubuntu) |
Fix Released
|
Low
|
Marco Trevisan (Treviño) | ||
Focal |
Fix Released
|
Low
|
Marco Trevisan (Treviño) | ||
Groovy |
Fix Released
|
Low
|
Marco Trevisan (Treviño) |
Bug Description
[ Impact ]
[13359.449610] fprintd[355436]: segfault at 0 ip 00007ffb9f375385 sp 00007ffddc26ba90 error 4 in libfprint-
See upstream bug: https:/
[ Test case ]
Build and run the tests included into libfprint to ensure this doesn't happen anymore
as the upstream sources include an umockdev based device that simulates the actual device interaction for enroll an verification.
Also monitor: https:/
Otherwise: user testing
[ Regression potential ]
Capture doesn't happen properly
Changed in libfprint (Ubuntu Groovy): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
importance: | Undecided → Low |
status: | New → In Progress |
Changed in libfprint (Ubuntu Focal): | |
assignee: | nobody → Marco Trevisan (Treviño) (3v1n0) |
importance: | Undecided → Low |
status: | New → In Progress |
description: | updated |
To post a comment you must log in.
This bug was fixed in the package libfprint - 1:1.90. 3+tod1- 0ubuntu2
--------------- 3+tod1- 0ubuntu2) hirsute; urgency=medium
libfprint (1:1.90.
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resubmitting commands.
This also needs proper commands cancellation (LP: #1897613)
- Add support for new Synaptics devices IDs (LP: #1905593)
- Fix vfs301 verification using device pointer on callbacks (LP: #1905597)
- Ensure we do not waste power for unsupported devices (LP: #1905603)
- Add identification support to synaptics driver.
It allows to unlock / log-in with any finger. (LP: #1905600)
-- Marco Trevisan (Treviño) <email address hidden> Wed, 25 Nov 2020 19:18:20 +0100