Comment 6 for bug 255727

Revision history for this message
nZain (patrick-stalph) wrote :

So, after searching from here to upstream, from the non-duplicate upstream bug to forum posts, out-of-date PPAs I ask myself if this can be resolved somehow.
The upstream bug refers to problems where applications do not open on the correct monitor. However, this is not the issue here: when monitor 2 is gone, the gnome-panel resorts to the available monitor - which is of course useful in many respects. Typically, you don't want your applications be left alone in the void.

BUT when working in a dualscreen environment and from time to time only on a single monitor, this is just so anyoing. This issue is open for a long time.

So, I'm fine with the behavior as default: always revert back to an available monitor, if the original target is lost somehow. However, for the scenario depicted in this bug, it should be possible to "lock" a particular panel to a particular monitor, even if it is not showing then.

Basically, I suggest to add an option "right-click on the panel > preferences" to force a monitor, even if not present.
This raises the issue of "lost" panels, so eventually there should also be the possibility to "gather lost panels", e.g. by "right-click on any panel > find lost panels from disconnected monitors". I could live without the second - advanced - option, since I know where to look in the gconf.

If all this stuff confuses the majority of users that have only one monitor or always work with two mons, I'm also fine with a gconf option to deactivate this "save switching" off. My current workaround involves removing the whole panel from the list of visible panels... and re-inserting, if my second monitor becomes available. Mah.