Bug 179475

Summary: konsole will not response to keyboard after holding shift+right
Product: [Applications] konsole Reporter: epocher <xijiaosdq>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description epocher 2009-01-03 12:26:21 UTC
Version:           4.1.85 (using Devel)
Compiler:          gcc-4.3.2 x86_64-pc-linux-gnu-4.3.2
OS:                Linux
Installed from:    Compiled sources

After I have been holding shift+right/left for several seconds, konsole will not response to any keyboard striking any more.
I met this problem from version 4.1.0 to 4.1.85.
Just hold shift+right for several seconds, then you will need to close all konsole processes to come back.
Comment 1 Dario Andres 2009-01-03 16:03:13 UTC
Here using:

Qt: 4.4.3 + qt-copy-patches-889120
KDE: 4.1.87 (KDE 4.1.87 (KDE 4.2 >= 20090101))
kdelibs svn rev. 904849 / kdebase svn rev. 904849
on ArchLinux x86_64 - Kernel 2.6.27.10

I can't reproduce the bug ( even holding SHift+Right for 10 seconds) .
Are you using a non-default settings, how tabs do you have when you reproduce the bug ? Is any program running inside Konsole ?

After the "keyboard hang" , can you click on the menus or something ? (may be not only the keyboard doesn't work but the whole app is hang)
Comment 2 epocher 2009-01-04 11:21:40 UTC
I can still reproduce the problem.
If konsole have more than one tab, the problem occurs, even when nothting is running inside it.
I have tried rm ~/.kde4.2/share/config/konsolerc and ~/.kde4.2/share/apps/konsole.

Only the keyboard doesn't work, konsole is still alive. I can copy and run a command with the mouse.

I'm using:
Qt: 4.4.2
KDE: 4.1.87

Maybe it has been solved in version 4.1.87. I will upgrade to 4.1.87 as soon as possible.
Comment 3 epocher 2009-01-05 04:42:40 UTC
I upgrade to KDE-4.1.87 today (It should be 4.1.85 in my last message. There is a misstake.), and the problem has gone.

Thanks.