Version: Version 4.00.98 (using KDE 4.0.98) Installed from: Fedora RPMs OS: Linux I am using NVIDIAs TwinView running two different screens next to each other. On each screen there is a panel with an taskbar at the bottom. Each taskbar is configured to show just the applications running currently on the selected screen. Basically everything works fine, however after using "run command..." the task isn't removed from the taskbar. So running this function several times leads to a taskbar filled completly with tasks that actually does not exist anymore. All other application seems to working fine and are removed like expected after they had been closed. "Run command" seems the only application that actually fails. In fact these tasks still have a context menu that is not reacting on any command. The problem seems to be related to the setting "Only show tasks from the current screen". If this option isn't used, everything is working fine again.
This broke sometime in the last two/three weeks.
*** Bug 168572 has been marked as a duplicate of this bug. ***
It's not strictly only krunner, I also had it happening with a kde copying dialogue. And I can confirm that it comes with the setting "Only show tasks from the current screen".
I can confirm this bug on 4.1.0.
same problem here. Debian, KDE 4.1, Nvidia 173.14.12
also happends with VLC. A field "VLC (XVideo output)" stays open.
*** This bug has been marked as a duplicate of bug 164852 ***
*** Bug 171569 has been marked as a duplicate of this bug. ***
I'm not so sure this is a duplicate bug. This bug is still present in KDE 4.1.3, reproduce by creating a panel on each screen in Twinview. Be sure to have task manager widgets on both, and have seperate screen focus and active mouse screen enabled. Also be sure to have the taskbar only show tasks for their respective screens. Now start krunner, and a 'Run Command' item will remain in the panel with no option to close it working. Thanks, Pieter
Sorry, not just start krunner (alt + f2) , but run something too.
> This bug is still present in KDE 4.1.3 of it's still in 4.1.3: i only fixed it yesterday! the fix will be in 4.2.0 unless someone decides to backport it to the 4.1 branch. that would be fine, but i personally have no time for backporting between now and 4.2.0