Version: 1.6.6 (using 3.5.9, Kubuntu (hardy) 4:3.5.9-0ubuntu7.1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.24-16-generic 1) Open konsole. 2) Type "ls /". 3) Press TAB. 4) Try closing the konsole window. On my system I get the message that konsole is no longer responding. If I cancel the warning message, go back to konsole and press TAB again, konsole is suddenly gone. There might be a hidden reason for all that strange behaviour but it does not really makes sense from a users perspective.
Does it make any difference if you change the notification style via Settings -> Bell?
Unfortunately not. I tried all four signal options and the result is always the same.
> If I cancel the warning message, go back to konsole and > press TAB again, konsole is suddenly gone. Can you run Konsole from another terminal (eg. xterm) and see if any warning messages are printed to the output?
There is only one warning when I start up konsole: --------------- $ konsole kdecore (KProcess): WARNING: _attachPty() 16 --------------- No other messages appear, even when I press TAB and try to close konsole.
Does killing knotify4 make any difference (via "killall -9 knotify4"), apart from stopping any notification sound effects or popups?
knotify4 is not running. This bugreport is for konsole 1.6.6 (KDE 3.5.9). knotify IS running but killing it does not change anything regarding this bug.
> knotify4 is not running. This bugreport is for konsole 1.6.6 (KDE 3.5.9). Sorry, my mistake. Can you please install debug packages for KDE (kdelibs-dbg, kdebase-dbg) and run Konsole from gdb: > gdb konsole >> run When going back to the Konsole window after it freezes and pressing Tab, go back to gdb and see whether Konsole has exited normally or if it has crashed - in which case enter "backtrace" to get a listing of which part of the program caused the problem.
> When going back to the Konsole window after it freezes... Konsole does not freeze completely. Although the error message that says that konsole is no longer responding, it is still possible to use the menus and edit the current line. It just suddenly exits after pressing TAB or return. > go back to gdb and see whether Konsole has exited normally or if it has crashed It has exited normally.
> Konsole does not freeze completely. Although the error message > that says that konsole is no longer responding, That is unusual. There are a few more things to try: 1. If you run Konsole with the --noclose argument, does the terminal window remain open when it previously exited unexpectedly? 2. Does the memory usage of Konsole or the shell program increase noticeably after Tab is pressed? 3. Does it make a difference which shell you use (eg. bash, zsh or fish)?
> If you run Konsole with the --noclose argument, does the terminal window remain open when it previously exited unexpectedly? No, konsole exits even with the --noclose argument. > Does the memory usage of Konsole or the shell program increase noticeably after Tab is pressed? No, not at all. > Does it make a difference which shell you use (eg. bash, zsh or fish)? Konsole exits immediately if I try the four steps given in the original bug report with zsh or fish. I was wondering if it is more efficient if you could reproduce the problem locally. I just tried the Kubuntu 8.04 install CD (download from here http://www.kubuntu.org/download.php) and could reproduce the problem. Maybe it is more efficient than the current bouncing of trial-and-error messages between us. But I do not mind assisting in finding the source of the bug...
> I just tried the Kubuntu 8.04 install CD (download from here > http://www.kubuntu.org/download.php) and could reproduce the problem Do you mean running from the live CD? In that case I'll download it and try that.
> Do you mean running from the live CD? Yes, exactly. I mean the live CD. Sorry, "install CD" was a little imprecise...
I just tested with Konsole 2.1 from KDE 4.1.1. The bug is still there but the effects are different. Please try the following steps: 1) Open Konsole from the start menu. 2) Type "ls /". 3) Press TAB. 4) Close the Konsole window. 5) Try again starting Konsole from the start menu. On my system (Kubuntu 8.04.1 with the KDE-4.1.1 packages) Konsole does not start up any more at step (5).
The bug is still present in KDE-4.2 beta1.
The bug is still present in KDE-4.2 rc1.
The bug is still present in KDE-4.2.2.
The bug is still present in KDE 4.3 Beta2.
Hi Ronny, You're welcome to remind us that the problem still persists for you but I don't expect it to magically fix itself. I have not been able to reproduce and I haven't seen similar reports. You'll have to try and pinpoint the problem first. You said that it doesn't happen if you use zsh/fish instead of bash? If so, can you try another terminal such as gnome-terminal or xterm and see if it still happens?
> I have not been able to reproduce OK, let's then try to make sure that you can reproduce the problem. Here are the verbose instructions: 1) Download the Kubuntu 9.04 CD from http://www.kubuntu.org/getkubuntu/download 2) Burn it to a CD. 3) Boot your computer with this CD. 4) Open Konsole from the start menu. 5) Type "ls /" (without return or anything else besides the four quoted characters). 6) Press TAB once (and only *ONCE*). 7) Close the Konsole window. 8) Try again starting Konsole from the start menu. What happens now? Here Konsole never starts up again...
I reproduced it running 4.3.0 (kubuntu) following steps in #19 4-8. When I try to start konsole from the menu the 2nd time, I get a 'bouncing ball' (I guess that's what it is) for a few seconds. It will start from xterm, but not system menu.
Whatever on earth the reason was for this very strange bug, it magically fixed itself in KDE-4.3.2 (Just tried with Kubuntu 9.10): $ konsole -v Qt: 4.5.2 KDE: 4.3.2 (KDE 4.3.2) Konsole: 2.3.2