Version: (using Devel) Installed from: Compiled sources Some times Krunner begin to have such behavior: 1) It`s begin to dissapear after I have typed some part or full command 2) When I have typed the command I press ented but nothing happens 3) When I use backspace it crashes, and I can`t save backtrace because backtrace window also disapears after several seconds...
I never stumbled over such behaviour of Krunner. Does this still occur with recent versions like 4.2(RC1, beta,...)?
Something similar happens to me, too (with Debian 5.0 Lenny and KDE 4.2.0 from Debian Experimental). Not very often, but let's say 1 in every 100 times I press Alt+F2 and try to run something via krunner. I'm sorry I don't have a proper stack trace available at the moment. But I did start krunner from Konsole and tried to start konqueror. I was able to type "konq", after that krunner disappeared. This is what was thrown to my Konsole window. --- X Error: BadGC (invalid GC parameter) 13 Major opcode: 60 (X_FreeGC) Resource id: 0x4200e43 X Error: RenderBadPicture (invalid Picture parameter) 179 Extension: 157 (RENDER) Minor opcode: 8 (RenderComposite) Resource id: 0x4200e42 X Error: RenderBadPicture (invalid Picture parameter) 179 Extension: 157 (RENDER) Minor opcode: 7 (RenderFreePicture) Resource id: 0x4200e42 X Error: BadPixmap (invalid Pixmap parameter) 4 Major opcode: 54 (X_FreePixmap) Resource id: 0x4200e41 Qt-subapplication: Fatal IO error: client killed ---
bump.. any news about this bug for recent kde versions?
works for me when using KDE SC 4.8 beta2. Feel free to reopen if it still happens in recent version .