FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not working

[SamuelB.]

Fingerprint* not working after upgrade from 19.10 to 20.04

uname -r
5.4.0-29-generic

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal

dpkg --list |grep "^ii" | grep fingerprint|cut -d" " -f3
fprintd
libchromaprint1:amd64
libfprint-2-2:amd64
libfprint-2-tod1:amd64
libofa0:amd64
libpam-fprintd:amd64

When running systemctl status fprintd.service is degraded.
After restarting fprintd.service, it is again degraded as soon as e.g. fprintd-enroll is started:

fprintd-enroll samuel
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Message recipient disconnected from message bus without replying

fprintd-delete samuel
found 1 devices
Device at /net/reactivated/Fprint/Device/0
Using device /net/reactivated/Fprint/Device/0
failed to claim device: Message recipient disconnected from message bus without replying

tail -f /var/log/syslog
May 12 11:19:14 laptop dbus-daemon[1077]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.220' (uid=1000 pid=6766 comm="fprintd-enroll samuel " label="unconfined")
May 12 11:19:14 laptop systemd[1]: Starting Fingerprint Authentication Daemon...
May 12 11:19:15 laptop dbus-daemon[1077]: [system] Successfully activated service 'net.reactivated.Fprint'
May 12 11:19:15 laptop systemd[1]: Started Fingerprint Authentication Daemon.
May 12 11:19:15 laptop fprintd[6767]: free(): invalid pointer
May 12 11:19:15 laptop systemd[1]: fprintd.service: Main process exited, code=dumped, status=6/ABRT
May 12 11:19:15 laptop systemd[1]: fprintd.service: Failed with result 'core-dump'.

Before upgrade to 20.04 everything worked.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

[SamuelB. (bw-sammy)]

```
G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log fprintd-enroll samuel
```

[Sebastien Bacher (seb128)]

Thanks, it seems fprintd itself is the process having the issue though

Could you install the debug package for it by following the steps on https://wiki.ubuntu.com/Debug%20Symbol%20Packages or just getting https://launchpad.net/ubuntu/+source/fprintd/1.90.1-1ubuntu1/+build/19168508/+files/fprintd-dbgsym_1.90.1-1ubuntu1_amd64.ddeb

Then use valgrind

$ sudo valgrind /usr/libexec/fprintd

then do the enroll/trigger the bug, and attached the log there

[SamuelB. (bw-sammy)]

==18347== Memcheck, a memory error detector
==18347== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==18347== Using Valgrind-3.15.0 and LibVEX; rerun with -h for copyright info
==18347== Command: /usr/libexec/fprintd
==18347==
--18347-- WARNING: unhandled amd64-linux syscall: 315
--18347-- You may be able to write your own handler.
--18347-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--18347-- Nevertheless we consider this a bug. Please report
--18347-- it at http://valgrind.org/support/bug_reports.html.

(fprintd:18347): libfprint-SSM-CRITICAL **: 10:20:37.541: fpi_ssm_next_state: assertion 'machine != NULL' failed
^C==18347==
==18347== Process terminating with default action of signal 2 (SIGINT)
==18347== at 0x7CCC96F: poll (poll.c:29)
==18347== by 0x49A01AD: ??? (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.2)
==18347== by 0x49A0532: g_main_loop_run (in /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6400.2)
==18347== by 0x10EADD: ??? (in /usr/libexec/fprintd)
==18347== by 0x7BDE0B2: (below main) (libc-start.c:308)
==18347==
==18347== HEAP SUMMARY:
==18347== in use at exit: 238,943 bytes in 2,382 blocks
==18347== total heap usage: 11,420 allocs, 9,038 frees, 1,756,218 bytes allocated
==18347==
==18347== LEAK SUMMARY:
==18347== definitely lost: 211 bytes in 3 blocks
==18347== indirectly lost: 254 bytes in 5 blocks
==18347== possibly lost: 4,272 bytes in 38 blocks
==18347== still reachable: 214,830 bytes in 2,188 blocks
==18347== of which reachable via heuristic:
==18347== length64 : 2,144 bytes in 47 blocks
==18347== newarray : 1,680 bytes in 25 blocks
==18347== suppressed: 0 bytes in 0 blocks
==18347== Rerun with --leak-check=full to see details of leaked memory
==18347==
==18347== For lists of detected and suppressed errors, rerun with: -s
==18347== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[SamuelB. (bw-sammy)]

log w/o ^C
started as follows:

sudo systemctl stop fprintd.service
sudo valgrind --leak-check=full /usr/libexec/fprintd

then tried to add fingerprint via GUI

[Sebastien Bacher (seb128)]

There is no error in the valgrind log, still that warning could be useful
(fprintd:34283): libfprint-SSM-CRITICAL **: 16:11:04.879: fpi_ssm_next_state: assertion 'machine != NULL' failed

did you get the bug when you get the log?

[SamuelB. (bw-sammy)]

did you get the bug when you get the log?: Not sure if I understand the question correctly. The libfprint-SSM-CRITICAL Message occurs as soon as I try to register a fingerprint (via GUI or fprintd-enroll)

[Sebastien Bacher (seb128)]

I mean did you try to use fprintd-enroll and did it fail the same way as before?

[SamuelB. (bw-sammy)]

I did not check, if /usr/libexec/fprintd fails WITHOUT calling fprintd-enroll. It seems to do so:

sudo valgrind --leak-check=full /usr/libexec/fprintd &> valgrind3.log

[SamuelB. (bw-sammy)]

The message
(fprintd:10028): libfprint-SSM-CRITICAL **: 10:43:16.840: fpi_ssm_next_state: assertion 'machine != NULL' failed
appears, when fprintd-enroll is applied.

Terminal 1: sudo valgrind --leak-check=full /usr/libexec/fprintd &> valgrind4.log
Terminal 2: sudo fprintd-enroll right-index-finger samuel

/usr/libexec/fprintd fails either way...

[Sebastien Bacher (seb128)]

Thanks, unsure why those don't show an error when using gdb you had a segfault

Ccing Marco who might have an idea there

[SamuelB. (bw-sammy)]

Maybe this helps:

sudo systemctl start fprintd

try to enroll via GUI

output of syslog:
May 27 11:50:38 scc-ej4555-01 systemd[1]: Starting Fingerprint Authentication Daemon...
May 27 11:50:38 scc-ej4555-01 systemd[1]: Started Fingerprint Authentication Daemon.
May 27 11:50:44 scc-ej4555-01 fprintd[53018]: free(): invalid pointer
May 27 11:50:44 scc-ej4555-01 systemd[1]: fprintd.service: Main process exited, code=dumped, status=6/ABRT
May 27 11:50:44 scc-ej4555-01 systemd[1]: fprintd.service: Failed with result 'core-dump'.
May 27 11:50:47 scc-ej4555-01 gnome-control-c[52854]: gtk_widget_set_visible: assertion 'GTK_IS_WIDGET (widget)' failed
May 27 11:50:47 scc-ej4555-01 kernel: [ 7271.791188] gnome-control-c[52854]: segfault at 8 ip 00007f709d2ac6cf sp 00007ffcd44e1730 error 4 in libgtk-3.so.0.2404.14[7f709d20c000+36f000]
May 27 11:50:47 scc-ej4555-01 kernel: [ 7271.791221] Code: 25 28 00 00 00 0f 85 f5 00 00 00 48 83 c4 48 5b 5d 41 5c 41 5d c3 0f 1f 44 00 00 48 89 ef e8 a8 ef ff ff 48 8b 43 68 48 89 ef <48> 8b 70 08 e8 08 93 28 00 48 8b 7b 38 44 89 e6 e8 2c 49 15 00 48
May 27 11:50:47 scc-ej4555-01 systemd[1368]: gnome-launched-gnome-control-center.desktop-52854.scope: Succeeded.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[carlosv (cvedovatti)]

Same issues with "Validity VFS301"

[marcus (marcuspratley)]

This has been fixed upstream by the looks of things. Guess a backport is in order?

https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/144

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

Yes, a libfprint version has been released recently and so I will prepare an SRU soon.