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: ``` [+] ./2018/07/IMG-20180705-WA0004.jpg [1] 594036 segmentation fault fdupes -r -d -I . ``` I then used fdupes to find this particular file and copied that file and it's duplicate to /tmp/test to repeat the test in a more limited environment and that gave the same result. I then created a new test file in a new directory and copied that to make a duplicate. Same result. I then used fdupes on the test directory in ncurses mode and marked one, pressed delete, and exited the application. Thus, it seems the only thing that I could find that triggers this is the combination of the commandline options as both location and actual files involved don't change the outcome and interactive mode works. -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-2-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fdupes depends on: ii libc6 2.31-4 ii libncursesw6 6.2+20200918-1 ii libpcre2-32-0 10.34-7 ii libtinfo6 6.2+20200918-1 fdupes recommends no packages. fdupes suggests no packages. -- no debconf information
