Version: 2.0 (using 4.0.3 (KDE 4.0.3), compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.23.12-52.fc7 I start some kde4 application, such as ksysguard, by typing in konsole, $ksysguard Then I close ksysguard and return to konsole. $ Now I find that konsole stops responding to keyboard. The problem can solved just by changing the current window to another program, or opening another tab. If I open another tab by double clicking the bottom bar, then both tabs of the konsole respond. But after I close the new tab, the konsole stops responding again. This problem occurs repeatedly here. I'm in Fedora 7 and LANG="zh_CN.UTF-8". I compile the kde4.0.3 by myself. I found the same problem in kde4.0.2 release.
> Now I find that konsole stops responding to keyboard. Does sending Ctrl+Z, Ctrl+C or Ctrl+D do anything? Can you run Konsole from another terminal (eg. xterm) and see if any warnings or error messages are displayed.
I try a little more and find that it may not be a bug of konsole, but a bug of kde4 system? Because I run xterm or urxvt (rxvt-unicode), run kde4 program with the same way, then the same problem occurs, just as konsole. None of Ctrl+Z, Ctrl_C or Ctrl+D helps. But there is some difference between them. For xterm, after I run ksysguard then close ksysguard, xterm stops to respond the keyboard. But When I move the xterm window a little, xterm works well again. For urxvt, moving the urxvt window does not help. But exchanging the current window helps. For konsole, moving the konsole window does not help either. Unfortunately I compile and build the kde4.0.3 with the option -DCMAKE_BUILD_TYPE=Release I do not see any error message output, when I run Konsole from xterm. Maybe there are something wrong in kde4 for switching the keyboard to another active window when the current window is closed?
It occurs that some kde4 programs stop to respond the keyboard at the same time when I'm trying, such as the search bar on the menu of plasma, all konsole windows. But dolphin and konqueror respond. None of the operations I have said helps. I close all the konsoles, then start a new one, it responds again.
> I try a little more and find that it may not be a bug of konsole, but > a bug of kde4 system? It might be a KWin issue? Does running a different window manager instead (eg. metacity) make any difference? eg. With metacity installed, from a terminal run: metacity --replace
I cannot reproduce here. Closing until a reply to comment #4 is posted.