Hide Forgot
Description of problem: I'm running system on laptop and I'm using two monitor setup, regular monitor and laptop display. Regular monitor is the primary one. When I undock laptop, all windows from primary monitor move to laptop display, which is expected. But when I get laptop back to dock, all windows stay on laptop screen. This is pretty annoying. I have to move all windows to their original location. Version-Release number of selected component (if applicable): gnome-shell-3.8.4-2.fc19 gnome-shell-3.8.4-10.el7 How reproducible: always Steps to Reproduce: 1. see description Additional info: I'm running Fedora 19 but same issue appear on rhel-7.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This seems to work fine on GNOME-3.14 except that it doesn't with the very first undock/dock event since the gnome session start. Reproducer: 1. In GNOME, set up a layout such that both the laptop's display and an external display is used 2. Make the external display primary 3. Open two windows and place one on each screen 4. Undock and dock 6. Notice how both windows remain on the laptop's display (incorrect behavior) 7. Move one of them back to the external display 8. Undock and dock 9. Now the windows are placed in their original locations, i.e. one of them being on the external display (correct behavior) Logging out and in again, the same scenario is repeated.
Revisiting this issue, it actually turns out to be pretty random in terms of reproducibility. I would say it depends on whether the secondary display is ready at the time gnome-shell tries to restore individual windows. So if the display on which a window was before undocking doesn't activate fast enough on docking, the window will just end up on the display which is already active.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.