FS#17817 - ^C no longer sends SIGINT

Attached to Project: Arch Linux
Opened by Jeff Cook (cookiecaper) - Wednesday, 13 January 2010, 03:56 GMT
Last edited by Allan McRae (Allan) - Saturday, 16 January 2010, 07:06 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

^C no longer sends SIGINT, apparently. It won't kill anything I try to kill, it's not an issue of an ignored thing. killall doesn't seem to work either, but pkill -9 does. See http://bbs.archlinux.org/viewtopic.php?pid=687265 for forum thread about this.

This is highly annoying and I would like it to get fixed.

Additional info:
* package version(s)
Fully up-to-date x86_64 installation as 1/12/2010 8:55 PM MST

* config and/or log files etc.


Steps to reproduce:

Update your system, go to your terminal, hit Ctrl-C, observe that nothing happens.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 16 January 2010, 07:06 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Martin Kühne (mar77i) - Wednesday, 13 January 2010, 23:29 GMT
^C works fine here on urxvt and xterm windows.
please supply a logically consistent way how to reproduce this bug:
* what terminal are you using and with what configuration
* what x config (keyboard layout)
* xev output for ctrl+C
* what else could cause the system to behave this way.
Comment by Thomas Dziedzic (tomd123) - Thursday, 14 January 2010, 15:31 GMT
I also can not reproduce this bug. I think the title of this bug is misleading in that, it probably is sending a SIGINT, but the application itself is hanging. You could use pkill -2 appname to send an INT signal manually if you want to check if ^C is not sending the signal.
Also, please post specific instructions on how you can reproduce this bug.
Comment by Jeff Cook (cookiecaper) - Thursday, 14 January 2010, 15:41 GMT
I don't believe it's a case of the application hanging. The application remains operable and accepts other input, just ignores ^C. I also tested with many different applications to see if that was the deal or not. pkill -2 does _not_ close the process, but pkill -9 does... perhaps it's something broken with SIGINT itself, then?

I will follow-up with the details requested in first reply soon.
Comment by Thomas Dziedzic (tomd123) - Friday, 15 January 2010, 14:40 GMT
Forum post: http://bbs.archlinux.org/viewtopic.php?id=88645 (on going conversation)
Comment by Jeff Cook (cookiecaper) - Friday, 15 January 2010, 15:48 GMT
Attached is the output of several presses of ^C in xev, my .Xdefaults file, and xorg.conf. Let me know if you need other files.

I am using urxvt, but I get the same results in gnome-terminal.

I've found that ^C in tty (that is, not in X) works as expected on yaourt and find.

VLC is the only application I've found so far which responds correctly to a ^C in X. Everything else seems to ignore it, though "^C" is printed on the terminal.

Using kernel26 2.6.32.3-1, xorg-server 1.7.3.902-1, and nvidia 190.53-3 on x86_64.
   xev_output (26 KiB)
   Xdefults (3.6 KiB)
   xorg.conf (2.9 KiB)
Comment by Jeff Cook (cookiecaper) - Friday, 15 January 2010, 16:40 GMT
Forgot that Xorg.0.log might be useful, adding that.
   Xorg.0.log (13.8 KiB)
Comment by Jeff Cook (cookiecaper) - Friday, 15 January 2010, 19:49 GMT
I've fixed it now; it was something with the version of awesome I was using. I cleared it out and installed the awesome from the repositories and all is well now.

Thanks to all who've helped with this.

Loading...