gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050

[Thovi]

[ Impact ]

When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying".

For information, my fingerprint sensor is :
- lsusb
Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor

[ Test case ]

With a fingerprint reader 138a:0050:
 - Open gnome-control-center user-accounts
 - Select the fingeprint row to enroll a finger
 - Follow the procedure and the finger should be enrolled
 - Verify with:
   fprintd-list $USER

[ Regression potential ]

 - The fingerprint is not read by the sensor

---

Ubuntu 20.04

gnome-control-center:
  Installé : 1:3.36.1-1ubuntu5
  Candidat : 1:3.36.1-1ubuntu5
 Table de version :
 *** 1:3.36.1-1ubuntu5 500
        500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages
        100 /var/lib/dpkg/status

What I expected to happen, is that everything works and that I can set up my finger for unlocking.

What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying".

ProblemType: BugDistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.1-1ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 22:00:30 2020
InstallationDate: Installed on 2020-05-11 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=fr_BE:fr
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_BE.UTF-8
 SHELL=/bin/bashSourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Sebastien Bacher (seb128)]

Could you also add your 'journalctl -b 0' log after getting the issue?

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Thovi (thovi98)]

Here is, in attachment, the backtrace as asked.

And here is the result of 'journalctl -b 0' :

-- Logs begin at Mon 2020-05-11 18:06:04 CEST, end at Wed 2020-05-13 10:44:17 CEST. --
mai 13 10:28:08 HP-ENVY-Notebook kernel: microcode: microcode updated early to revision 0xd6, date = 2019-10-03
mai 13 10:28:08 HP-ENVY-Notebook kernel: Linux version 5.4.0-29-generic (buildd@lgw01-amd64-035) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #33-Ubuntu SMP Wed Apr 29 14:32:2>
mai 13 10:28:08 HP-ENVY-Notebook kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=8b04a58c-b577-4888-aa18-76aa7e8b564e ro quiet splash vt.handoff=7
mai 13 10:28:08 HP-ENVY-Notebook kernel: KERNEL supported cpus:
mai 13 10:28:08 HP-ENVY-Notebook kernel: Intel GenuineIntel
mai 13 10:28:08 HP-ENVY-Notebook kernel: AMD AuthenticAMD
mai 13 10:28:08 HP-ENVY-Notebook kernel: Hygon HygonGenuine
mai 13 10:28:08 HP-ENVY-Notebook kernel: Centaur CentaurHauls
mai 13 10:28:08 HP-ENVY-Notebook kernel: zhaoxin Shanghai
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
mai 13 10:28:08 HP-ENVY-Notebook kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
mai 13 10:28:08 HP-ENVY-Notebook kernel: BIOS-provided physical RAM map:
mai 13 10:28:08 HP-ENVY-Notebook kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
mai 13 10:28:08 HP-ENVY-Notebook kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
mai 13 10:28:08 HP-ENVY-Notebook kernel: BIOS-e820: [mem 0x0000000000059000-0x0000000000085fff] usable

[Thovi (thovi98)]

I didn't find the ID when I ran ubuntu-bug, so I made step 2 @Daniel :
https://errors.ubuntu.com/oops/0521f384-94f4-11ea-9ae3-fa163e102db1

Don't hesitate to ask me more info, I will help as possible to make Ubuntu better and without bugs.

[Sebastien Bacher (seb128)]

Could you install gnome-control-center-dbgsym libgtk-3-0-dbgsym libglib2.0-0-dbgsym and get a new backtrace? (https://wiki.ubuntu.com/Debug%20Symbol%20Packages)

[Thovi (thovi98)]

I tried but I have dependency problems during the install of asked packages :

sudo apt install gnome-control-center-dbgsym libgtk-3-0-dbgsym libglib2.0-0-dbgsym
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation :

Les paquets suivants contiennent des dépendances non satisfaites :
 gnome-control-center-dbgsym : Dépend: gnome-control-center (= 1:3.36.2-0ubuntu1) mais 1:3.36.1-1ubuntu5 devra être installé
E: Impossible de corriger les problèmes, des paquets défectueux sont en mode « garder en l'état ».

[Sebastien Bacher (seb128)]

the version you are using comes from focal-proposed, you need to add a corresponding line for the ddeb archive

[Thovi (thovi98)]

Okay it worked, thanks !

Here is my attachment : I did this command : gdb gnome-control-center 2>&1 | tee ~/gdb-gnome-control-center-dbgsym.txt

Say me if I did something wrong.

Thanks again

[Sebastien Bacher (seb128)]

seems like something went wrong indeed

gnome-control-center-dbgsym: Aucun fichier ou dossier de ce type.
Starting program:
No executable file specified.'

are you sure you entered the right gnome-control-center name and didn't append -dbgsym? can you copy or screenshot the command line where you typed the command and the output?

[Thovi (thovi98)]

Oh yes, I'm sorry, I gave the wrong file, I don't understand :o
Here is the correct attachment, sorry for the trouble.

[Vishal Rao (vishalrao)]

Hello, I am also facing this issue with the same model fingerprint reader, my whoopsie ID is 8804bc49a3bfcc26ad40837d0a5c61aa09fdedf077a0466423734856fcf05e73fa02e0d83af85ec9fe0ad00f0a026473769f48ceaf022e02c6b59d8219f0e683

I will post further info shortly.

[Vishal Rao (vishalrao)]

My GDB output:

(gdb) run
Starting program: /usr/bin/gnome-control-center
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffeab84700 (LWP 7240)]
[New Thread 0x7fffea383700 (LWP 7241)]
[New Thread 0x7fffe3dec700 (LWP 7245)]
[New Thread 0x7fffe35eb700 (LWP 7246)]
[New Thread 0x7fffe2dea700 (LWP 7247)]
[New Thread 0x7fffe25e9700 (LWP 7248)]
[New Thread 0x7fffe1ac7700 (LWP 7249)]
[New Thread 0x7fffe12c6700 (LWP 7250)]
[New Thread 0x7fffe0a91700 (LWP 7252)]
[New Thread 0x7fffd7912700 (LWP 7253)]
[New Thread 0x7fffd6d11700 (LWP 7254)]
[Detaching after fork from child process 7255]
[Detaching after fork from child process 7262]
[Detaching after fork from child process 7284]
[Thread 0x7fffe1ac7700 (LWP 7249) exited]

(gnome-control-center:7236): Gtk-CRITICAL **: 19:33:17.519: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
0x00007ffff75c66cf in set_current_page (assistant=0x555556170dc0, page_num=1) at ../../../../gtk/gtkassistant.c:992
992 ../../../../gtk/gtkassistant.c: No such file or directory.
(gdb) bt
#0 0x00007ffff75c66cf in set_current_page (assistant=0x555556170dc0, page_num=1) at ../../../../gtk/gtkassistant.c:992
#1 0x00007ffff75c6adb in compute_next_step (assistant=assistant@entry=0x555556170dc0) at ../../../../gtk/gtkassistant.c:1041
#2 0x00007ffff75c6be7 in gtk_assistant_next_page (assistant=0x555556170dc0) at ../../../../gtk/gtkassistant.c:1610
#3 0x00007ffff7d8ba56 in _g_closure_invoke_va (closure=0x5555567f8e00, return_value=0x0, instance=0x55555631a180, args=0x7fffffffcbe0, n_params=0,
    param_types=0x0) at ../../../gobject/gclosure.c:873
#4 0x00007ffff7daab28 in g_signal_emit_valist (instance=0x55555631a180, signal_id=<optimized out>, detail=0, var_args=var_args@entry=0x7fffffffcbe0)
    at ../../../gobject/gsignal.c:3407
#5 0x00007ffff7dab0d3 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>)
    at ../../../gobject/gsignal.c:3554
#6 0x00007ffff75df2ae in gtk_button_do_release (emit_clicked=<optimized out>, button=0x55555631a180) at ../../../../gtk/gtkbutton.c:1845
#7 gtk_button_do_release (button=0x55555631a180, emit_clicked=<optimized out>) at ../../../../gtk/gtkbutton.c:1832
#8 0x00007ffff75df318 in gtk_real_button_released (button=0x55555631a180) at ../../../../gtk/gtkbutton.c:1963
#9 0x00007ffff7d8b802 in g_closure_invoke (closure=0x555555bc1ec0, return_value=0x0, n_param_values=1, param_values=0x7fffffffcef0,
    invocation_hint=0x7fffffffce70) at ../../../gobject/gclosure.c:810
#10 0x00007ffff7d9f962 in signal_emit_unlocked_R (node=node@entry=0x555555b87d90, detail=detail@entry=0, instance=instance@entry=0x55555631a180,
    emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffffffcef0) at ../../../gobject/gsignal.c:3672
#11 0x00007ffff7daab9e in g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>,
    var_args=var_args@entry=0x7fffffffd0a0) at ../../../gobject/gsignal.c:3498
#12 0x00007ffff7dab0d3 in ...

[Vishal Rao (vishalrao)]

My journalctl -b 0 output (tail portion) note it has the line:
May 14 21:12:35 envybird fprintd[3142]: free(): invalid pointer

[Vishal Rao (vishalrao)]

journalctl snippet:

May 14 21:17:01 envybird CRON[3407]: pam_unix(cron:session): session opened for user root by (uid=0)
May 14 21:17:01 envybird CRON[3408]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
May 14 21:17:01 envybird CRON[3407]: pam_unix(cron:session): session closed for user root
May 14 21:17:29 envybird gnome-shell[3174]: Fontconfig warning: Directory/file mtime in the future. New fonts may not be detected.
May 14 21:17:46 envybird dbus-daemon[804]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by>
May 14 21:17:46 envybird systemd[1]: Starting Fingerprint Authentication Daemon...
May 14 21:17:46 envybird dbus-daemon[804]: [system] Successfully activated service 'net.reactivated.Fprint'
May 14 21:17:46 envybird systemd[1]: Started Fingerprint Authentication Daemon.
May 14 21:17:46 envybird fprintd[3428]: free(): invalid pointer
May 14 21:17:46 envybird systemd[1]: fprintd.service: Main process exited, code=dumped, status=6/ABRT
May 14 21:17:46 envybird systemd[1]: fprintd.service: Failed with result 'core-dump'.
May 14 21:18:00 envybird gnome-shell[3174]: Fontconfig warning: Directory/file mtime in the future. New fonts may not be detected.
May 14 21:18:22 envybird rtkit-daemon[1276]: Supervising 4 threads of 2 processes of 1 users.
May 14 21:18:22 envybird rtkit-daemon[1276]: Supervising 4 threads of 2 processes of 1 users.
May 14 21:18:31 envybird gnome-shell[3174]: Fontconfig warning: Directory/file mtime in the future. New fonts may not be detected.
May 14 21:19:02 envybird gnome-shell[3174]: Fontconfig warning: Directory/file mtime in the future. New fonts may not be detected.

[Vishal Rao (vishalrao)]

Looks like known issue in fprintd code, bugs filed and probably fixed, see the following:

https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/64

and

https://gitlab.freedesktop.org/libfprint/fprintd/-/issues/54

[Vishal Rao (vishalrao)]

Probably this commit: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/90ccf9a0af6df135be09cebb0eeb5906e49d92a6

[Marco Trevisan (Treviño) (3v1n0)]

While g-c-c should probably not crash on errors, the main issue here is indeed that fprintd crashes, and given that the enroll UI is still something going to be deprecated so it's not worth to fix in here IMHO.

What we do need to fix is libfprint, so moving the bug there instead.

[Marco Trevisan (Treviño) (3v1n0)]

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

---------------
libfprint (1:1.90.2+tod1-0ubuntu1) groovy; urgency=medium

  * New upstream release
    - Fixed crash in VFS0050 (LP: #1876502)
    - Enrollment fails with UPEK reader (LP: #1881380)
    - Lots of various drivers fixes
    - As per a patch for nbis required for some sensors that was accidentally
      dropped in an earlier release. Users of sensors/drivers aes1610, aes2501,
      aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll
  * d/p/git_reading_pointer.patch:
    - Dopped (applied upstream)
  * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267)
  * debian/rules: Be strictier about symbol changes
  * libfprint-2-tod1.symbols: Add new TOD symbols

 -- Marco Trevisan (Treviño) <email address hidden> Fri, 19 Jun 2020 17:38:55 +0200

[Thovi (thovi98)]

Thanks for this update !! Looking forward to update it when the package is available :D

[Robie Basak (racb)]

An upload of libfprint to focal-proposed has been rejected from the upload queue for the following reason: "No bug references and/or SRU information for "New upstream release" and "Lots of various driver fixes"; incomplete discussion of regression potential in all bugs that are referenced. Please see https://wiki.ubuntu.com/StableReleaseUpdates for the required information and procedure.".

[Brian Murray (brian-murray)]

Hello Thovi, or anyone else affected,

Accepted libfprint into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libfprint/1:1.90.2+tod1-0ubuntu1~20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[SamuelB. (bw-sammy)]

Hello together,
works as expected.
Thanks!

Ubuntu 20.04, libfprint-2-2 1:1.90.2+tod1-0ubuntu1~20.04.1, FUJITSU LIFEBOOK U748

[Thovi (thovi98)]

Works great for me too !!
Thanks for the update !

[Launchpad Janitor (janitor)]

This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1~20.04.1

---------------
libfprint (1:1.90.2+tod1-0ubuntu1~20.04.1) focal; urgency=medium

  * New upstream release (LP: #1887822)
    - Fixed crash in VFS0050 (LP: #1878285)
    - Enrollment fails with UPEK reader (LP: #1881380)
    - As per a patch for nbis required for some sensors that was accidentally
      dropped in an earlier release. Users of sensors/drivers aes1610, aes2501,
      aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll
  * d/p/git_reading_pointer.patch:
    - Dopped (applied upstream)
  * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267)
  * debian/rules: Be strictier about symbol changes
  * libfprint-2-tod1.symbols: Add new TOD symbols
  * debian/{control, gbp.conf}: prepare for focal branching

 -- Marco Trevisan (Treviño) <email address hidden> Thu, 16 Jul 2020 18:06:19 +0200

[Łukasz Zemczak (sil2100)]

The verification of the Stable Release Update for libfprint has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.