After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 769098 - Fullscreen windows are raised to front when they don't have focus
Fullscreen windows are raised to front when they don't have focus
Status: RESOLVED DUPLICATE of bug 768221
Product: mutter
Classification: Core
Component: general
3.20.x
Other Linux
: Normal minor
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2016-07-22 20:08 UTC by Jonathan Doman
Modified: 2016-07-22 22:56 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jonathan Doman 2016-07-22 20:08:34 UTC
Using mutter 3.20.3 on Fedora 24.

Steps:
1. Open app A on monitor 1 (e.g. nautilus).
2. Open fullscreen app B on monitor 2 (e.g. Remmina, gnome-terminal).
3. Open non-fullscreen app C on monitor 2 and place over fullscreen window. Everything is fine at this point.
4. Switch focus back to app A on monitor 1. At this point, B has risen to front and C is no longer visible.

I expect that C should remain visible on top of B. I usually use fullscreen because it simplifies/improves the UI of a particular program - e.g. in a Remmina session I want to see the full screen of the remote computer without scaling or cropping. It's very useful to me to have a fullscreen window be in the background of everything else.

In general, the stacking priority of a fullscreen window seems to be too high. In the previous example, it's also impossible to drag app A above app C. You can drag it onto monitor 2 and it retains focus, but it's not visible until you move focus to B and then back to A. (Then once A is above B, you can drag it back and forth between monitors and it will stay on top - the rules are inconsistent/unexpected.)
Comment 1 Florian Müllner 2016-07-22 22:29:30 UTC
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 768221 ***
Comment 2 Jonathan Doman 2016-07-22 22:56:23 UTC
I did find that bug but it wasn't clear it was the same symptoms. Glad to hear it's been fixed. Thanks!