*** This bug is a duplicate of bug 1878285 ***
https://bugs.launchpad.net/bugs/1878285
** This bug has been marked a duplicate of bug 1878285
gnome-control-center crashes on setting up fingerprint
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878172
Title:
FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not working
Yes, a libfprint version has been released recently and so I will
prepare an SRU soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878172
Title:
FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors
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
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Same issues with "Validity VFS301"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878172
Title:
FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not working
To manage notifications about this bug
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libfprint (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878172
Title:
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 fpri
Thanks, unsure why those don't show an error when using gdb you had a
segfault
Ccing Marco who might have an idea there
** Changed in: libfprint (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
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-fing
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
** Attachment added: "valgrind3.log"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1878172/+attachment/5374591/+
I mean did you try to use fprintd-enroll and did it fail the same way as
before?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878172
Title:
FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not wo
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)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
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?
--
You received this bug notification because you are a member of
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
** Attachment added: "valgrind2.log"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1878172/+attachment/5373438/+files/valg
==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
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
```
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
```
** Attachment added: "valgrind.log"
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1878172/+attachment/5373224/+files/valg
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.
** Changed in: libf
18 matches
Mail list logo
