Package: debug-me Version: 1.20190926-2 Severity: normal On one of 3 bullseye installs, debug-me does not start up cleanly. After prompting for an email address, it opens the control terminal, with (apparently) a new instance of debug-me prompting for an email address. This continues ad infinitum as long as I keep hitting return at the email prompt. If I interrupt at the email prompt with ^C, then the most recent control window ends up with a debug-me session in it (or the initial window if I do this the first time). It seems a remote user can still connect to this session, but I don't imagine that emailing of logs works. [1]
I'm not sure what's different between these three testing installs. The one where this bug occurs is the newest, and probably has less packages installed. [1]: as an aside, I'm not sure emailing of logs is working in any case, but that requires more investigation/ -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE=en_CA:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debug-me depends on: ii libc6 2.31-3 ii libffi7 3.3-4 ii libgmp10 2:6.2.0+dfsg-6 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages debug-me recommends: ii debian-keyring 2020.06.24 ii gnupg 2.2.20-1 debug-me suggests no packages. -- no debconf information
