Version: (using Devel) OS: Linux Installed from: Compiled sources If you create a panel on the top of the desktop, icons will stay under it until you change the eight of the panel.
Created attachment 29308 [details] picture showing icons under the panel
Another precision : icons are still under the panel after a reboot.
I can confirm this, but only if panel is not maximized over whole screen edge. After I have consulted the code, it seem to that desktop compute where can widgets be from bounding rectangle of "free desktop space" (where are not drawn panels).. But bounding rect is whole screen when panel is not maximized..
*** Bug 180674 has been marked as a duplicate of this bug. ***
*** Bug 182750 has been marked as a duplicate of this bug. ***
Confirmed in trunk too.
I also experience this with horizontally maximized panels on the upper and lower edge; the icons are always about a half grid step above where they should be. [Besides, the grid seems to be kinda arbitrary, but that's another issue]
*** Bug 189498 has been marked as a duplicate of this bug. ***
I cannot confirm this with KDE 4.3 Beta1, instead of staying covered by the top screen panel the top icons are covered by the top panel just a split second and then instantly jump down below the panel - everytime I switch to the activity that uses the classic view (which is very annoying). See Bug 193591, maybe related?
SVN commit 979511 by aseigo: avoid all panels BUG:177722 M +12 -1 folderview.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=979511
*** Bug 191583 has been marked as a duplicate of this bug. ***
This problem comes back when you log out and back in with a new session. If you have your Task Manager along the top of the screen, using FolderView for your desktop, every time you log out and back in, your desktop icons will creep up the screen incrementally, and a scrollbar appears along the right side of the desktop.
Indeed, I also confirm comment #12 happening on KDE 4.3.3
Should this case be reopened, or should I file a new bug?
Filed new bug: bug#217092