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 619685 - Monitor Preferences does not have an option to set the primary monitor
Monitor Preferences does not have an option to set the primary monitor
Status: RESOLVED DUPLICATE of bug 588041
Product: gnome-control-center
Classification: Core
Component: Display
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-05-25 23:12 UTC by Thiago M. Sayão
Modified: 2010-05-26 16:30 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Monitor Preferences screenshot showing my configuration (36.15 KB, image/png)
2010-05-25 23:13 UTC, Thiago M. Sayão
Details

Description Thiago M. Sayão 2010-05-25 23:12:02 UTC
The Monitor Preferences does not have an option to set which monitor is the primary. I can set it with xrandr, like this:

xrandr --output DVI-I_2/digital --primary

But this does not work for a "normal" user. It would be very useful to have this option, because some gnome apps opens by default on the primary monitor, like the panel for example. If the user have plugged the monitors on the graphics card on the "wrong" order, the panel would open on the "wrong" monitor. It can be dragged, but it would be annoying to have to drag each app.
Comment 1 Thiago M. Sayão 2010-05-25 23:13:25 UTC
Created attachment 161983 [details]
Monitor Preferences screenshot showing my configuration
Comment 2 Thiago M. Sayão 2010-05-25 23:15:57 UTC
Also filed on launchpad:
https://bugs.launchpad.net/bugs/584372
Comment 3 Jens Granseuer 2010-05-26 16:30:13 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 bug 588041 ***