Version: (using KDE 4.4.0) Compiler: gcc (SUSE Linux) 4.4.1 [gcc-4_4-branch revision 150839] OS: Linux Installed from: openSUSE RPMs When I access the dashboard, either moving the mouse to a screen corner or with Ctrl+F12, I noticed there's a new process in the task manager called "plasma-desktop". The problem is when I access the dashboard when other applications are in the foreground, this "plasma-desktop" process doesn't have precedence over them. This means that in this case I have to click the "plasma-desktop" process to see the dashboard. This only seems to happen if I access the dashboard through a screen corner (I have it configured to the bottom-right corner). Ctrl+F12 works as expected. Also, after using Ctrl+F12 the mouse corner shortcut seems to work correctly for a while, but the problem starts happening again shortly. Additional information: my dashboard is configured to show a separate set of elements.
Also, the Analog Clock plasmoid I have in the dashboard sometimes isn't drawn correctly. I have to resize it for it to appear again. This happens with several Plasma Themes, including Air. I first noticed this behavior in 4.4 RC 1.
(In reply to comment #1) > Also, the Analog Clock plasmoid I have in the dashboard sometimes isn't drawn > correctly. I have to resize it for it to appear again. Feel free to CC to https://bugs.kde.org/show_bug.cgi?id=225824 Reassigning bug to plasma/dashboard, but wondering if this is more a kwin issue...
I can confirm this issue using KDE SC 4.4 from the official Kubuntu PPA. It only happens when I call the dashboard via screen corner and another application has the focus. After calling the dashboard and clicking on it, it comes to foreground and hiding/calling it again still brings it to foreground till another application becomes the focus. My dashboard doesn't show a seperate activity.
I just noticed that there is another report about the same issue, that is also holding a screenshot. *** This bug has been marked as a duplicate of bug 226281 ***
*** Bug 226672 has been marked as a duplicate of this bug. ***