==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)

-- 
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 go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1878172/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to