Hello Otto, if you still can reproduce the segfault then it might also be possible to install the package systemd-coredump.
That way a backtrace should show up in 'journalctl -e' giving some more details of where the segfault happens. This should get more informative if the fdupes-dbgsym gets installed. This would be another repo described in [1]. Kind regards, Bernhard [1] https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
