Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

^C no longer issues a sigint in any application I've tried. I'm using ArchLinux. This is highly bad and I need it fixed. All help appreciated.

EDIT: So, we've found that ^C is sending a SIGINT, but most things are ignoring it. This problem only exists within X; ^C on a real tty seems to be honored as expected. VLC responds to ^C within X, but I can't find anything else which does. A manual SIGINT via kill -2 seems to be ignored, too.

There are ongoing discussions on this issue at and .

share|improve this question
Are you on the local console, or connected in via ssh? If via ssh, what are you using as your local terminal? – Matt Simmons Jan 13 '10 at 3:52
I am on the local console. – user31557 Jan 15 '10 at 15:59

Try running stty -a, that should give you something like:

speed 38400 baud; rows 40; columns 80; line = 0;
intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = ;
eol2 = ; swtch = ; ...

The field you are interested in is "intr = ^C" (or whatever "intr" is set to for you). That tells you what key combination generates a SIGINT to the process that owns the terminal. To set it back to ^C, you'll need to be able to generate a ^C on the keyboard and the exact mechanism for doing that varies from shell to shell, but some quick testing indicates that for (at least) bash and ksh you do it by first pressing ^V (I have a vague memory that sufficiently old "plain sh" required \^C to insert a literal ^C on the line).

share|improve this answer
^V works in all programs that use the readline library, but appears to work in dash too. – grawity Jan 13 '10 at 13:55
Thanks for this. intr = ^C on mine, but we've made some progress. See my edits to the original question. – user31557 Jan 15 '10 at 15:57
Is the terminal set to "brkint" or "-brkint"? Similarly for "-ignbrk" and "ignbrk"? – Vatine Jan 20 '10 at 7:37
Additionally, you can (usually) get a half-decent "cooked IO" terminal by doing stty sane. – Vatine Jan 22 '10 at 11:51

Do you have a trap on SIGINT set in your shell?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.