GNOME Bugzilla – Bug 702728
Multimonitor - keep windows on the primary display
Last modified: 2021-07-05 14:40:04 UTC
I have an external monitor which I use as a primary display. When I plug in my laptop, my existing windows stay on the laptop display, and I have to manually move them over to the external, one at a time. It would be much more convenient if the windows were moved to the new primary display when it is connected.
This is probably a long time regression of bug 645408. GNOME should remember which windows were lastly used on a particular display in that particular configuration, and move them there. A simple example is: 1) Dual monitor setup: xchat on the internal monitor, firefox on the external monitor 2) Undock/disconnect external monitor -> both xchat and firefox on the internal monitor 3) Dock/connect external monitor again -> xchat stays on the internal monitor, firefox is moved to the external monitor, as in 1) What's even better, it is supposed to remember even workspaces, so it should not just move the app to the correct monitor, but even to the correct workspace. To be honest, I never remember it working, even some years back, although bug 645408 is marked as resolved. It would be great to have this fixed again, I must spend some time to manually shuffle windows every time I dock/undock my notebook.
There is a new gnome-shell extension which fixes this problem: https://github.com/aiguofer/return-to-monitor Maybe gnome-shell developers could simply take the code? It doesn't seem to be complicated. Thanks.
(In reply to comment #2) > Maybe gnome-shell developers could simply take the code? It doesn't seem to be > complicated. Filed as bug 731760.
Shall we mark this as fixed then?
No, bug 731760 did not fix this. After undocking, windows are kept at the correct workspaces, but after docking back, all windows are squashed to a secondary monitor to the first workspace.
Let's update the version field then. 3.22?
gnome-shell-3.22.2-2.fc25.x86_64
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/ Thank you for your understanding and your help.