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 567118 - In multi-screen setting, I cannot choose on which screen the gnome panel should be
In multi-screen setting, I cannot choose on which screen the gnome panel shou...
Status: RESOLVED DUPLICATE of bug 562944
Product: gnome-control-center
Classification: Core
Component: Display
2.24.x
Other All
: Normal enhancement
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2009-01-09 03:50 UTC by Paul Jones
Modified: 2009-03-05 18:17 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Paul Jones 2009-01-09 03:50:14 UTC 
If you set a dual-screen setup with gnome-display-properties, gnome-panel will
be only on one of those screens (the first display device listed by xrandr).
Unfortunately, it seems to be impossible to choose which one should be the
"main" one.

In my situation, with my laptop and a secondary monitor or projector the panel shows up on the secondary display. Thus if the secondary display is removed while the laptop is on I don't have access to the panel to access the applet or the menu. Not Good.

It would be nice if there was a button for default monitor in this application so I could choose which monitor I wanted the panel on.

(I copied and pasted parts of this bug report from bug 562944. This seems like a better place to file that bug).
Comment 1 Paul Jones 2009-01-09 16:24:38 UTC 
Further this bug just doesn't affect gnome-panel. The all of the icons on the Desktop and Avant Window Navigator show up on the wrong monitor.
Comment 2 Jens Granseuer 2009-03-05 18:17:03 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 562944 ***