(In reply to Christophe Fergeau from comment #3)
> backtrace of fprintd while it's hung
>
<snip>
> #19 0x00007fbcdda6f957 in sd_event_run (e=0x5627d5f75c10,
> timeout=18446744073709551615) at
> ../src/libsystemd/sd-event/sd-event.c:2690
> #20 0x00005627d4abc5a2 in manager_loop (m=0x5627d5f77520)
> at ../src/core/manager.c:2291
> #21 0x00005627d4a1ece1 in main (argc=5, argv=<optimized out>)
> at ../src/core/main.c:1937
This is clearly systemd, pre-fork. This code isn't from fprintd, and if stuff hangs before fprintd is even forked, I don't see how blaming it would help anything.
(In reply to Christophe Fergeau from comment #3) 184467440737095 51615) at libsystemd/ sd-event/ sd-event. c:2690 core/manager. c:2291 core/main. c:1937
> backtrace of fprintd while it's hung
>
<snip>
> #19 0x00007fbcdda6f957 in sd_event_run (e=0x5627d5f75c10,
> timeout=
> ../src/
> #20 0x00005627d4abc5a2 in manager_loop (m=0x5627d5f77520)
> at ../src/
> #21 0x00005627d4a1ece1 in main (argc=5, argv=<optimized out>)
> at ../src/
This is clearly systemd, pre-fork. This code isn't from fprintd, and if stuff hangs before fprintd is even forked, I don't see how blaming it would help anything.