View previous topic :: View next topic |
Author |
Message |
ville.aakko Tux's lil' helper
Joined: 06 Aug 2006 Posts: 113 Location: Oulu, Finland
|
Posted: Fri Nov 08, 2013 5:06 pm Post subject: CTRL+C broken in Konsole... |
|
|
Hi!
I apologize if this has already been brought up elsewhere. I found similar issues via google (even on this forum), but they were years old and the solutions didn't work for me.
Pressing CTRL+C is half-way broken in Konsole. It doesn't usually work, but in some cases, it does work. If a program is started, ^C is echoed, but depending on the program, it seems not to receive the signal - or does.
List of example cases where CTRL+C DOES NOT work:
- First and foremost: I can't cancel a command line in bash! (no ^C echoed)
- Exit from sleep (I can't exit the loop: while true ; do sleep 1s ; done)
- dd -command
- cat -command
- mplayer
CTRL+C is echoed in all but the first case, but the program is never exited. I can use CTRL+D (to bg a process), however...
This is on Konsole 4.10.5 (and kde-meta-4.10.5). I'm using nvidia drivers (in the past, some version was causing similar problems) version 331.20.
I have tried deleting all settings relating to konsole in ~/.kde4/. I have nothing bound to CTRL+C (as it is echoed, if a program is running - but not if there a line being typed in bash!).
CTRL+C DOES WORK in xterm. Don't have other terminal emulators available (I think).
Curiously, if I start a screen session in a VT, and attach to it from konsole, CTRL+C does work in it - and vice versa!.
So, maybe KDE / Konsole sets some weird environment variable(s)?
Any ideas where to look further for? _________________ - Ville |
|
Back to top |
|
|
ville.aakko Tux's lil' helper
Joined: 06 Aug 2006 Posts: 113 Location: Oulu, Finland
|
Posted: Sat Nov 09, 2013 4:35 pm Post subject: |
|
|
Anyone?
This is driving me nuts! (and, is outright dangerous... imagine typing 'rm -R * ' (without enter) [CTRL+C] 'ls -l' ....
I have tried moving ~/.kde4 out of the way, and removing .bashrc and .bash_profile. I have compared environments from a screen session started in xterm or a VT and in konsole (the CTRL+C does not work only in the last case). Am I really the only one with this bug? I'd presume there are others using the same konsole / KDE version, if it works for them, then tehre must be something weird on my system...
Also, edited the subject accordingly (I only thought CTRL+C worked somewhere, but it actually doesn't - I was probably confused by screen sessions started elsewhere, but the behaviour is very constant).
Cheers! _________________ - Ville |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Sat Nov 09, 2013 6:16 pm Post subject: Re: CTRL+C broken in Konsole... |
|
|
ville.aakko wrote: | I'm using nvidia drivers (in the past, some version was causing similar problems) version 331.20. |
Could be the culprit.
What happens if you downgrade to nvidia-drivers-319.49 ? _________________
|
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Sat Nov 09, 2013 7:26 pm Post subject: |
|
|
I would rather search the konsole bugs upstream at kde.org, or upgrade to kde-4.11?
Code: | ral@maci:~$ while sleep 11 ; do echo a; done
^C
ral@maci:~$ qlist -Iv nvidia
x11-drivers/nvidia-drivers-331.20
|
|
|
Back to top |
|
|
ville.aakko Tux's lil' helper
Joined: 06 Aug 2006 Posts: 113 Location: Oulu, Finland
|
Posted: Sat Nov 09, 2013 8:07 pm Post subject: |
|
|
Well I'll be d*ed:
Code: | $ qlist -Iv nvidia-drivers
x11-drivers/nvidia-drivers-319.60
22:03:59 VillenVDRdevil:~
$ while true ; do sleep 1s ; done
^C^C^C^Z
[1]+ Pysäytetty sleep 1s
$ ps
PID TTY TIME CMD
15117 pts/15 00:00:00 bash
15368 pts/15 00:00:00 sleep
15369 pts/15 00:00:00 ps |
But:
Code: | $ qlist -Iv nvidia-drivers
x11-drivers/nvidia-drivers-319.49
22:03:59 VillenVDRdevil:~
$ while true ; do sleep 1s ; done
^C
$ |
Maybe someone can confirm so we can start bugging nvidia
Cheers! _________________ - Ville |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Sat Nov 09, 2013 8:10 pm Post subject: |
|
|
ville.aakko wrote: | Maybe someone can confirm! |
I believe I wouldn't have advised you to downgrade nvidia if I had not previously confirmed.
Could be helpful to have your say there : https://bugs.gentoo.org/show_bug.cgi?id=487558 _________________
|
|
Back to top |
|
|
cmdic n00b
Joined: 06 Apr 2012 Posts: 27
|
Posted: Sun Nov 24, 2013 10:14 pm Post subject: |
|
|
yes I am running: 331.17
Will this be patched soon or should I downgrade? |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Sun Nov 24, 2013 10:18 pm Post subject: |
|
|
cmdic wrote: | yes I am running: 331.17
Will this be patched soon or should I downgrade? |
I presume it all depends on you wanting your system to be working soon or to be operational now. _________________
|
|
Back to top |
|
|
uraes Tux's lil' helper
Joined: 28 Nov 2002 Posts: 135 Location: Estonia
|
Posted: Sat Dec 07, 2013 9:37 pm Post subject: |
|
|
damned...
downgrading to 325.15 needs
Code: |
* <sys-kernel/gentoo-sources-3.11
* <sys-kernel/vanilla-sources-3.11
|
so no latest-greatest kernels ... |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Sat Dec 07, 2013 9:44 pm Post subject: |
|
|
Downgrade to 304.116 _________________
|
|
Back to top |
|
|
uraes Tux's lil' helper
Joined: 28 Nov 2002 Posts: 135 Location: Estonia
|
Posted: Sun Dec 08, 2013 10:50 am Post subject: |
|
|
aCOSwt wrote: | Downgrade to 304.116 |
alrighty! that helped, thanks aCOSwt! |
|
Back to top |
|
|
johnny99 Apprentice
Joined: 24 Oct 2005 Posts: 249 Location: Berkeley, California
|
Posted: Wed Dec 18, 2013 12:05 am Post subject: |
|
|
Downgraded to 325.15 fixed my problem. 331.20 has problems. |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Wed Dec 18, 2013 7:27 am Post subject: |
|
|
johnny99 wrote: | Downgraded to 325.15 fixed my problem. 331.20 has problems. |
325.15 had less problems but was definitely concerned.
Anyway, it is *not* an option :
Quote: | 14 Dec 2013; Jeroen Roovers <jer@gentoo.org> -nvidia-drivers-325.15.ebuild: Old. |
_________________
|
|
Back to top |
|
|
chrisstankevitz Guru
Joined: 14 Dec 2003 Posts: 472 Location: Santa Barbara, CA, USA
|
Posted: Fri Dec 20, 2013 9:21 pm Post subject: |
|
|
This sucks. What the heck are the nvidia driver developers doing that disables CTRL-C??? |
|
Back to top |
|
|
aCOSwt Bodhisattva
Joined: 19 Oct 2007 Posts: 2537 Location: Hilbert space
|
Posted: Fri Dec 20, 2013 9:54 pm Post subject: |
|
|
According to user's observations they seem playing with the signal mask.
According to nvidia devs... hmm... can't really know, they claimed not being able to reproduce this issue (and related). _________________
|
|
Back to top |
|
|
smeat n00b
Joined: 09 Nov 2013 Posts: 2
|
|
Back to top |
|
|
ulenrich Veteran
Joined: 10 Oct 2010 Posts: 1480
|
Posted: Sat Dec 21, 2013 1:00 pm Post subject: |
|
|
I doubt it. But I was not hit by this bug.
Is the ebuild procps involved?
(Recently a version bump I saw I happen to have USE unicode active) |
|
Back to top |
|
|
|