Crash with fprintd 1.92.0

Bug #1944369 reported by Antoine Bertin
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
Fix Released
Critical
Andy Chi
libfprint-2-tod1-goodix
Opinion
Critical
boger.wang
libfprint (Ubuntu)
Fix Released
Critical
Marco Trevisan (Treviño)

Bug Description

When using this with fprintd 1.92.0 and onwards I get:

    /usr/lib/fprintd: symbol lookup error: /usr/lib/fprintd: undefined symbol: fp_device_has_feature, version LIBFPRINT_2.0.0

See more comments here: https://aur.archlinux.org/packages/libfprint-2-tod1-xps9300-bin/

Revision history for this message
Vincent Gerris (vgerris) wrote :

I can confirm the crash, so this is affecting the 22.04 (Jammy) release.
It also triggers a Gnome login bug on it - no users is visible.
Would be great if a fix can be made.
I filed a bug for fprintd that I closed because this was the problem.
Related bugs

https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633
https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1962344

Andy Chi (andch)
Changed in libfprint-2-tod1-goodix:
assignee: nobody → Andy Chi (andch)
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Andy Chi (andch) wrote :

Hello @vegerris,
Can you help to upload the file under /var/lib/fprint/goodix/?

Thanks.

Revision history for this message
Vincent Gerris (vgerris) wrote :

hi, there are multiple files. .dat and .log. .dat I presume?
it's attached.

Revision history for this message
Andy Chi (andch) wrote :

Hi @vegerris,
Can you also upload .log file? I'll send to Goodix developer for check.

Revision history for this message
Andy Chi (andch) wrote :

Upload log of tod-goodix-driver

tags: added: oem-priority originate-from-1965879 somerville
Changed in oem-priority:
status: New → Confirmed
importance: Undecided → Critical
assignee: nobody → Andy Chi (andch)
Changed in libfprint-2-tod1-goodix:
assignee: Andy Chi (andch) → boger.wang (bogerwang)
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

I thought I made sure we were ABI-compatible here, it seems not the case?

I need to check the symbols again then.

Changed in libfprint-2-tod1-goodix:
status: Confirmed → Opinion
Changed in libfprint (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
importance: Undecided → Critical
Revision history for this message
Andy Chi (andch) wrote (last edit ):

Hello @3v1n0,
It won't crashed after update to testing version 1.94.3.
The attached file is the log from 1.94.3-tod1.

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

The crash itself is fixed by the latest upload, but please Andy report a new bug for the identification bug, to be solved in an upcoming upload.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu1

---------------
libfprint (1:1.94.3+tod1-0ubuntu1) jammy; urgency=medium

  * New upstream release (LP: #1944369)
  * debian/libfprint-2-2.postinst: Devices triggers updated
  * debian/libfprint-2-tod1.symbols: Add new symbols
  * debian/docs: Update README name to use markdown file
  * tod: Ensure we install tod-macros.h header

 -- Marco Trevisan (Treviño) <email address hidden> Sun, 27 Mar 2022 23:48:11 +0200

Changed in libfprint (Ubuntu):
status: New → Fix Released
Revision history for this message
Andy Chi (andch) wrote (last edit ):

fprintd won't crash with new libfprint version on Jammy which is 1:1.94.3+tod1-0ubuntu1.

Changed in oem-priority:
status: Confirmed → Fix Released
Revision history for this message
Andy Chi (andch) wrote :

Hello @3v1n0,
I opened a new Bug #1966911 to track identification failed. Please refer to that one.

Revision history for this message
Vincent Gerris (vgerris) wrote :

I can confirm this version no longer crashes with the goodix driver. I am unable to make the fingerprint reader work, it enrolls with an error and complains about no storage. Seperate issue I suppose? thanks for the fix.

Revision history for this message
Andy Chi (andch) wrote :

@vgerris,
The separate issue is Bug #1966911

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.