Description of problem: Focus changes to secondary monitor when switching workspaces in the primary monitor. Version-Release number of selected component (if applicable): Fedora 22 $ uname -r 4.1.10-200.fc22.x86_64 $ gnome-shell --version GNOME Shell 3.16.3 How reproducible: Always Steps to Reproduce: 1. Plug an external monitor to your laptop 2. Open the Display settings and configure the built-in monitor as SECONDARY and the external monitor as PRIMARY 3. Open three distinct windows, e.g. 3 gnome-terminal windows: one in the only workspace in the SECONDARY monitor, and one in each of two workspaces in the PRIMARY monitor primary monitor - workspace 1 +------------------------------------------+ | | secondary monitor | | | +-------------------+ | +-------------------------+ | | | | | | | | A | | | +-------------+ | | | | | | | B | | | | | | | | | | | +-------------------+ | | +-------------+ | | | | | | | +-------------------------+ +------------------------------------------+ workspace 2 (initially not visible) +------------------------------------------+ | | | | | +-------------------+ | | | C | | | | | | | | | | | +-------------------+ | | | | | +------------------------------------------+ 4. Focus on the terminal A; you should have A and B visible, while your eyes are focused on A. 5. Change from workspace 1 to workspace 2 (e.g., using super+pgdown) Actual results: Focus is now on the terminal window B. Expected results: Focus should be in terminal window C, i.e., focus should have stayed in the same monitor that you're looking at. Additional info: The problem is reproducible even if PRIMARY=built-in and SECONDARY=external. Workspace switching with multiple monitors seemed to work the way described in the expected results a couple of weeks ago.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This is still a bug in Fedora 24. Nothing has changed. https://bugzilla.gnome.org/show_bug.cgi?id=653085
Still the case in Fedora 25.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.