Package: dpkg Version: 1.20.7.1 Followup-For: Bug #931402 I can reproduce this in just the shell that's started. Ctrl-C doesn't seem to have any immediate effect. However once the shell is exited, the Ctrl-C causes dpkg to terminate early.
I suspect that dpkg isn't creating a new foreground process group, so the SIGINT from Ctrl-C is being delivered to dpkg instead of the shell (or relevant sub-process like the editor). Adding a setsid or setpgid call somewhere in spawn_shell and/or show_diff would probably fix it. -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (700, 'testing'), (650, 'stable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dpkg depends on: ii libbz2-1.0 1.0.8-4 ii libc6 2.30-2 ii liblzma5 5.2.4-1+b1 ii libselinux1 3.1-2+b2 ii tar 1.29b-2 ii zlib1g 1:1.2.11.dfsg-2 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 2.1.20 pn debsig-verify <none> -- no debconf information
