journalctl -f | grep -E 'fpslave|sailfish-fpd'
and then unlocked it via fingerprint etc. - no output.
Then I went into settings and added another fingerprint.
Still no output.
Then I tried to add another fingerprint although there already were 5.
That’s when I got this:
fpslave: fpenroll_enter: QUIRK: cap to 5 fingerprints
sailfish-fpd: mrcontrol_set_fperror: error: FPERROR_NONE -> FPERROR_NO_SPACE
sailfish-fpd: mrcontrol_fphal_timeout_cb: fp hal is stuck; terminating
fpslave: fpcontrol_master_rd_cb: unexpected master wakeup: condition=0x10
sailfish-fpd: *** SLAVE TERMINATE
fpslave: fpcontrol_master_rd_cb: disabling master io watch
sailfish-fpd: main: sailfish-fpd terminating with exit value 1
systemd: sailfish-fpd.service: Main process exited, code=exited, status=1/FAILURE
systemd: sailfish-fpd.service: Failed with result 'exit-code'.
systemd: sailfish-fpd.service: Service hold-off time over, scheduling restart.
systemd: sailfish-fpd.service: Scheduled restart job, restart counter is at 2.
fpslave: fpsettings_scan_directory: /usr/lib/sailfish-fpd: can't open directory: No such file or directory
(removed date and host and some entries for easier reading)
find / -type d -name sailfish-fpd 2>/dev/null
fpsettings_scan_directory rightly complains about a missing directory, but I don’t think it matters.
If you go through your journal, you’ll find tons of similar entries. Unless they are very clearly labeled as (fatal) errors - don’t worry.