Package: ncurses-base
Version: 5.7+20090803-2
Severity: critical
Justification: breaks unrelated software
ctrl-c does no longer cause SIGINT.
Debugging this issue:
When I create a new xterm (or rxvt) as a fork from my windowmanager
(awesome) the terminal shows the broken behaviour.
I have still some xterms that are not affected open. Those were started
in 2009.
Using strace on both working and a broken xterm show that both send \3
to the terminal fd when I press ctrl-c.
stty on a working xterm looks like:
speed 38400 baud; line = 0;
On a broken xterm it looks like:
speed 38400 baud; line = 0;
-brkint -imaxbel
Using stty brkint imaxbel or stty sane does not solve the issue. Also
stty intr ^C does not help.
Starting a xterm from an working xterm results in a working xterm.
Starting a xterm from a broken xterm results in a broken xterm.
Starting a xterm, starting vim within it and then doing :!xterm<CR>
produces a working xterm.
Saving the environment of a working xterm, loading it in a broken xterm
and then starting a new xterm results in a broken xterm.
Do you have any other ideas for debugging the issue?
If you feel that I have assigned the bug report to the wrong package,
please reassign it to the correct package.
Helmut
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24.3
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages ncurses-base depends on:
ii libncurses5 5.7+20090803-2 shared libraries for terminal hand
Other packages of interest:
ii bash 4.1-1 The GNU Bourne Again SHell
ii rxvt 1:2.6.4-14 VT102 terminal emulator for the X Window System
ii xterm 253-1 X terminal emulator
ncurses-base recommends no packages.
ncurses-base suggests no packages.
-- no debconf information