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 568547 - All fullscreen windows are automatically raised on focus
All fullscreen windows are automatically raised on focus
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: Focus
2.24.x
Other All
: Normal minor
: ---
Assigned To: Thomas Thurman
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2009-01-21 13:05 UTC by Jakub Hrozek
Modified: 2020-11-06 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Jakub Hrozek 2009-01-21 13:05:01 UTC
Please describe the problem:
I'm running a dual head setup with most applications running in fulscreen mode (not just maximized, really fulscreen, activated with F11). The problem is, that all fullscreen running applications seem to be gaining focus at the expense of non-fullscreen when just one of them gets focus. The steps to reproduce describe the problem more easily, I think..

Steps to reproduce:
1. Get a dual head GNOME setup, the rest is pretty much defaults
2. Open a fullscreen application on both heads
3. On one head, have a non-fullscreen application on top, having focus. The non-fulscreen app is now correctly overlapping the fullscreen application.
4. Select the other fullscreen app on the other head


Actual results:
Both fullscreen windows are raised, even the one on first head that was not selected.

Expected results:
Only the window that got focus is selected

Does this happen every time?
Yes

Other information:
Comment 1 André Klapper 2020-11-06 20:07:03 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.