Version: (using Devel) Compiler: 4.3.2 OS: Linux Installed from: Compiled sources See attached screenshots. First shot "konq" was typed, but five different icons appeared, three of which seem to be irrelevant. More serious is the second screenshot, which shows overlapping icons. Besides uncluttering the icons, I think some usability gains can be made by only turning on a few of the runners by default.
Created attachment 29345 [details] krunner after typing "konq"
Created attachment 29346 [details] krunner after typing "kcalc"
for some reason, which i haven't tracked down yet, it seems that sometimes some icons get "forgotten" about and so sort of just hang about. this causes the problem you're seeing. "I think some usability gains can be made by only turning on a few of the runners by default" that obviously doesn't make much sense, as the entire point of krunner is provide possible matches.
*** Bug 176819 has been marked as a duplicate of this bug. ***
I still see this in KDE 4.2 beta 2. Makes krunner nearly useless as a search tool. I note that the "forgotten" icons are faded as if they were supposed to be animated away. Also I note that the window doesn't shrink down. This didn't happen with KDE 4.1.
*** Bug 180436 has been marked as a duplicate of this bug. ***
*** Bug 180510 has been marked as a duplicate of this bug. ***
confirming on kde 4.2 Beta2 too
I can confirm this with openSUSE packages version 4.1.87.
I still see this occasionally in 4.1.96 (rc1). One way (only that I've found) to clean it is to exit krunner and restart it. Haven't been able to figure out what the trigger is for it though.
*** Bug 180848 has been marked as a duplicate of this bug. ***
Created attachment 30655 [details] KRunner with KTorren and OpenOffice.org overlaps Some times the [Enter] key will actually select the icon that appears which has zero relation to what I have typed.
This happens to me also in KDE 4.2rc on Debian Sid/Experimental from deb http://kde42.debian.net/debian/ UNRELEASED main
I can confirm this, I'm seeing the issue pretty frequently with krunner in KDE 4.2.
Created attachment 30850 [details] krunner after typing kate I am also confirming the same in KRunner (Run Command Interface: 0.1), KDE 4.2.00 in Ubuntu 8.10. Thanks a lot...
I have seen this across multiple distros. Please ask if you need more information.
I think I found the cause for this bug. It is a race condition in workspace/krunner/interfaces/default/resultitem.cpp. As I understand it, if the ResultItem is remove()d while there is a call to animationComplete pending then the item is not properly deleted. The reason is that remove() starts an animation and connects the finished() signal of that animation to deleteLater(). In theory this animation should just run through and at the end cause the item to delete itself. The problem arises if before the end of the animation the pending call to animationComplete() is made: this function simply deletes the _current_ animation (which is the new one and not the one which caused animationComplete to be called in the first place) and therefore prevents the remove() animation from ever signaling finished() and therefore deleting the ResultItem. Long story short, the attached stop-gap style patch fixes the problem for me.
Created attachment 31062 [details] proposed patch
Just tested the patch and it appears to work fine. I was experiencing this issue on pretty much every use of krunner, but I have not been able to reproduce it after applying the patch.
*** Bug 183663 has been marked as a duplicate of this bug. ***
Luca Gugelmann: the patch seems to make sense: can you commit?
Fixed with Luca's patch, thanks a lot Luca! See http://lists.kde.org/?l=kde-commits&m=123410970515259&w=2 for the reference commit.
SVN commit 923352 by gugelmann: CCBUG:177815 Fixes confused and overlapped icons in krunner which are sometimes left over from previous queries. (backport from trunk.) M +9 -4 resultitem.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=923352
*** Bug 183871 has been marked as a duplicate of this bug. ***
*** Bug 184056 has been marked as a duplicate of this bug. ***
*** Bug 185007 has been marked as a duplicate of this bug. ***
*** Bug 186713 has been marked as a duplicate of this bug. ***