Comment 1 for bug 1888495

@Jesús, can you please provide a stacktrace for the crash?

You should be able to get one by calling fprintd-verify first, then Ctrl+C, meanwhile you run this:

sudo gdb -p $(pgrep -U fprintd -x fprintd) -batch \
  -ex "set logging on" -ex continue \
  -ex "bt full" \
  -ex quit

And that should catch the crash and save it as gdb.txt