I could indeed reproduce that:
Stack trace of thread 3038787:
#0 0x556080008e0b log_file_remaining (fdupes + 0xbe0b)
#1 0x55608000315a deletesuccessor (fdupes + 0x615a)
#2 0x55608dd8 main (fdupes + 0x3dd8)
#3 0x7f46c8255d0a __libc_start_main (libc.so.6 + 0x26d0a)
#4
I think this is fixed upstream in 2.1.2; see
https://github.com/adrianlopezroche/fdupes/commit/c0dd064bb02b5496e1ef51fcc9eed11dd08b6268
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
Package: fdupes
Version: 1:2.1.1-1
Severity: normal
Dear Maintainer,
while trying to clean up I encountered a segfault in fdupes. The
commandline I used was: `fdupes -r -d -I .`. It prints the first match
of a set of matches followed by the segfault:
```
[+]
4 matches
Mail list logo
