hi, it seems it does not start.
output from terminal:
ubuntu@ubuntu-inspiron-5482:~$ sudo apt install fprintd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
fprintd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/97,4 kB of archives.
After this operation, 680 kB of additional disk space will be used.
Selecting previously unselected package fprintd.
(Reading database ... 424549 files and directories currently installed.)
Preparing to unpack .../fprintd_1.94.1-1_amd64.deb ...
Unpacking fprintd (1.94.1-1) ...
Setting up fprintd (1.94.1-1) ...
fprintd.service is a disabled or a static unit not running, not starting it.
Processing triggers for dbus (1.12.20-2ubuntu2) ...
Processing triggers for man-db (2.10.1-1) ...
ubuntu@ubuntu-inspiron-5482:~$ systemctl restart fprintd.service
Job for fprintd.service failed because a fatal signal was delivered to the control process.
See "systemctl status fprintd.service" and "journalctl -xeu fprintd.service" for details.
ubuntu@ubuntu-inspiron-5482:~$ systemctl status fprintd.service
× fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/system/fprintd.service; static)
Active: failed (Result: signal) since Thu 2022-02-17 00:20:25 CET; 15s ago
Docs: man:fprintd(1)
Process: 33083 ExecStart=/usr/libexec/fprintd (code=killed, signal=SEGV)
Main PID: 33083 (code=killed, signal=SEGV)
CPU: 531ms
feb 17 00:20:23 ubuntu-inspiron-5482 systemd[1]: Starting Fingerprint Authentication Daemon...
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process exited, code=killed, status=11/SEGV
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with result 'signal'.
feb 17 00:20:25 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint Authentication Daemon.
ubuntu@ubuntu-inspiron-5482:~$ journalctl -xeu fprintd.service
░░
░░ The job identifier is 2235.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Main process exited, code=killed, status=11/SEGV
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit fprintd.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 11.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: fprintd.service: Failed with result 'signal'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit fprintd.service has entered the 'failed' state with result 'signal'.
feb 15 16:45:17 ubuntu-inspiron-5482 systemd[1]: Failed to start Fingerprint Authentication Daemon.
░░ Subject: A start job for unit fprintd.service has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ A start job for unit fprintd.service has finished with a failure.
░░
░░ The job identifier is 2235 and the job result is failed.
hi, it seems it does not start.
output from terminal:
ubuntu@ ubuntu- inspiron- 5482:~$ sudo apt install fprintd 1.94.1- 1_amd64. deb ... ubuntu- inspiron- 5482:~$ systemctl restart fprintd.service ubuntu- inspiron- 5482:~$ systemctl status fprintd.service system/ fprintd. service; static) /usr/libexec/ fprintd (code=killed, signal=SEGV)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
fprintd
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/97,4 kB of archives.
After this operation, 680 kB of additional disk space will be used.
Selecting previously unselected package fprintd.
(Reading database ... 424549 files and directories currently installed.)
Preparing to unpack .../fprintd_
Unpacking fprintd (1.94.1-1) ...
Setting up fprintd (1.94.1-1) ...
fprintd.service is a disabled or a static unit not running, not starting it.
Processing triggers for dbus (1.12.20-2ubuntu2) ...
Processing triggers for man-db (2.10.1-1) ...
ubuntu@
Job for fprintd.service failed because a fatal signal was delivered to the control process.
See "systemctl status fprintd.service" and "journalctl -xeu fprintd.service" for details.
ubuntu@
× fprintd.service - Fingerprint Authentication Daemon
Loaded: loaded (/lib/systemd/
Active: failed (Result: signal) since Thu 2022-02-17 00:20:25 CET; 15s ago
Docs: man:fprintd(1)
Process: 33083 ExecStart=
Main PID: 33083 (code=killed, signal=SEGV)
CPU: 531ms
feb 17 00:20:23 ubuntu- inspiron- 5482 systemd[1]: Starting Fingerprint Authentication Daemon... inspiron- 5482 systemd[1]: fprintd.service: Main process exited, code=killed, status=11/SEGV inspiron- 5482 systemd[1]: fprintd.service: Failed with result 'signal'. inspiron- 5482 systemd[1]: Failed to start Fingerprint Authentication Daemon. ubuntu- inspiron- 5482:~$ journalctl -xeu fprintd.service inspiron- 5482 systemd[1]: fprintd.service: Main process exited, code=killed, status=11/SEGV www.ubuntu. com/support inspiron- 5482 systemd[1]: fprintd.service: Failed with result 'signal'. www.ubuntu. com/support inspiron- 5482 systemd[1]: Failed to start Fingerprint Authentication Daemon. www.ubuntu. com/support
feb 17 00:20:25 ubuntu-
feb 17 00:20:25 ubuntu-
feb 17 00:20:25 ubuntu-
ubuntu@
░░
░░ The job identifier is 2235.
feb 15 16:45:17 ubuntu-
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://
░░
░░ An ExecStart= process belonging to unit fprintd.service has exited.
░░
░░ The process' exit code is 'killed' and its exit status is 11.
feb 15 16:45:17 ubuntu-
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://
░░
░░ The unit fprintd.service has entered the 'failed' state with result 'signal'.
feb 15 16:45:17 ubuntu-
░░ Subject: A start job for unit fprintd.service has failed
░░ Defined-By: systemd
░░ Support: http://
░░
░░ A start job for unit fprintd.service has finished with a failure.
░░
░░ The job identifier is 2235 and the job result is failed.
there is also a bug here : https:/ /bugs.launchpad .net/ubuntu/ +source/ fprintd/ +bug/1933633 that may be related?
Thanks for the heads up, hope these things will be solved.
Still seems like a good idea in the context of this bug to handle fprintd not working gracefully?