Version: (using KDE KDE 3.5.5) Installed from: Fedora RPMs OS: Linux Occasionally after a reasonable period of use, a Konsole window will stop responding to the keyboard. I cannot type anything in the shell, switch tabs or do anything with the keyboard. However, mouse input works perfectly, to the extent that I can right-click and paste commands into the shell and they are executed as usual. Trying to give SIGCONT or pressing Ctrl+Q does not help. I cannot seem to notice anything in particular that causes this to happen but I am usually SSH-ed in to a remote server. This happens to me once every few days. If I try and open another tab or window using the menu system and the mouse, there is still no response. However, when I start a new session from the panel, keyboard response is fine. No other applications are affected by this. Running KDE 3.5.5 on Fedora Core 5, using the default repository packages.
Are you still able to navigate the menus with the keyboard when Konsole appears to have frozen the keyboard. eg. If you click on one of the main menu items using the mouse, are you then able to move up and down the menus using the up/down arrows on the keyboard? > I cannot seem to notice anything in particular that causes > this to happen but I am usually SSH-ed in to a remote server Does killing the ssh program 'unfreeze' the keyboard? (start a new Konsole instance and run "killall -9 ssh") > However, when I start a new session from the panel, > keyboard response is fine. This starts a new application, rather than creating a new window for the existing program.
> Are you still able to navigate the menus with the keyboard when Konsole appears > to have frozen the keyboard. eg. If you click on one of the main menu items > using the mouse, are you then able to move up and down the menus using the > up/down arrows on the keyboard? Yes, I am able to navigate the main menu items using the keyboard after clicking once with the mouse. However, "Alt+S" key for example will not bring up the Session menu. > Does killing the ssh program 'unfreeze' the keyboard? No it doesn't. Although the SSH window does show "Killed." In addition, I can actually exit the ssh sessions in the frozen Konsole window gracefully by copying and pasting "exit (enter)" from any text editor.
OK, the ssh thing may be a red herring. This just happened to me again, and I was only logged on locally, just typing make.
I have been having this problem happen infrequently as well but I am using Ubuntu Gutsy wth KDE 3.5.7. The exact same situation is happening to me. I believe I ran a strace against the konsole process running and I get the following being repeated over and over again. select(26, [3 4 5 7 9 11 13 15 17 19 21 23 25], [], [], {0, 9795}) = 1 (in [23], left {0, 9795}) read(23, "\"\\\"\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\"..., 1024) = 364 gettimeofday({1188358259, 842301}, NULL) = 0 gettimeofday({1188358259, 842470}, NULL) = 0 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1188358259, 842505}, NULL) = 0 select(26, [3 4 5 7 9 11 13 15 17 19 21 23 25], [], [], {0, 9796}) = 1 (in [23], left {0, 9796}) read(23, "\"\\\"\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\"..., 1024) = 364 gettimeofday({1188358259, 842590}, NULL) = 0 gettimeofday({1188358259, 842761}, NULL) = 0 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1188358259, 842795}, NULL) = 0 select(26, [3 4 5 7 9 11 13 15 17 19 21 23 25], [], [], {0, 9795}) = 1 (in [23], left {0, 9795}) read(23, "\"\\\"\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\"..., 1024) = 364 gettimeofday({1188358259, 842881}, NULL) = 0 gettimeofday({1188358259, 843052}, NULL) = 0 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1188358259, 843086}, NULL) = 0 select(26, [3 4 5 7 9 11 13 15 17 19 21 23 25], [], [], {0, 9795}) = 1 (in [23], left {0, 9795}) read(23, "\"\\\"\\\\\\\"\\\\\\\\\\\\\\\"\\\\\\\\\\\\\\\\\\\\\\\\"..., 1024) = 364 gettimeofday({1188358259, 843181}, NULL) = 0
Reopen if you can duplicate this in KDE4. KDE3 is not maintained at this point.
I am having this problem with KDE4 (4:4.2.2-0ubuntu4). Usually switching to another window using Alt-Tab and then switching back again will fix the problem.