Version: unspecified (using KDE 4.4.95) OS: Linux I've got a two monitor configuration, this is why I can notice this bug. If you set one window to fullscreen (either via F11 in browsers or via the Window menu -> Advanced -> Fullscreen available to every window) then all other windows of that program (doesn't matter whether same process or different one) get always on top until you restore the fullscreen window to normal. For example: I have a dolphin window on the right monitor, I fullscreen it (or you can do it with your browser when watching videos). Now I have another dolphin window on the left monitor, I cannot get any windows cover it, the dolphin is just on top of everything, dolphin even covers windows that are set manually as Always on top via the window menu. Reproducible: Always Steps to Reproduce: See problem description
I'm not sure if it is a bug or a wanted feature. At least for modal dialogs it's required to have them as keep above or they would be below the fullscreen window.
I don't think this is a wanted feature. Because ALL of the instances are always on top, not just the fullscreen one!
layer.cpp:896 Active fullscreen windows should be on top of everything except for their modals & popups - but not other group members, so "this->group() == top->group()" is (imo rather) wrong and should be sth. like "this == top->transientFor()" - but i've no multiscreen setup to test
You could set up a KDE installation on Virtualbox, this allows you to set multiple screens (opens multiple windows, even if you only have on screen)
I noticed, that even krunner gets below those windows. Dashboard and panels seem to be in front.
Fixed by http://commits.kde.org/kde-workspace/10cd4faa8a0cb0619ebcfd462ee0104b1db58171 see BUG 293265
Not necessarily, or even rather not. Check bug #261799 and https://bugs.kde.org/show_bug.cgi?id=293265#c5
this should be -nearly- fixed, at least what you see is. remaining issue i was pointed to by private mail is for fullscreen windows on other virtual desktops which remain "fullscreen" because kwin decides that by stack and not by layer what also causes bug #296076 I'll however close this one.