Version: (using KDE 4.0.83) Installed from: SuSE RPMs On my desktop, I have two panels: the default at the bottom and an additional one at the top. This works great, with one exception: sometimes the titlebar of windows end up beneath the top-panel making it necessary to use the alt key to drag the window. Certainly doable if you know that little trick (although I have been fooled a few times...wondering why the window wouldn't close when trying to hit the "X" before realizing I clicked on the panel instead of the window) but shouldn't the windows be prohibited from being partially obscured by the panels?
can you try running with a difference windowmanager for a few days to see if this problem happens with them as well (e.g. blackbox or metacity)?
Sure. No problem. I'll get back to you on Wednesday at the latest.
Okay, I've been using metacity for a while now (I can do it for a while longer if you deem it necessary, although I have to say: I can't understand how the Gnome-guys can stand it) and so far the bug hasn't surfaced. Admittedly, it didn't show up often when using Kwin either (mostly but not exclusively when Gwenview was asked to show a picture that wouldn't fit between the panels) but when it did it was very annoying. Oh, and another behavior that didn't show up when I used metacity. I first thought it was a Kontact related problem (that I somehow never got around to reporting). Kontact is always running on my computer, iconified into the systray when I'm not using it. When I click on the systray icon (using Kwin) it is deiconified but stays in the taskbar and I have to click on the taskbar entry to bring it to the front. Using metacity, I got the behavior I expected: Kontact being both deiconified and brought up to the front and maximized.
if you can try to reproduce it in metacity but can't after the same general time it would take to appear when running kwin, then the experiment is probably completed. i'll re-assign to kwin.
Then I would say it's completed...during that period of time I would definately have expected to have run into that kind of behavior a couple of times.
Okay, it seems this bug has vanished as of RC1. It has not surfaced again so far at least. I'll mark this as resolved, and will re-open if the bug shows up again.