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 563750 - gnome-display-properties definitely overrides xorg.conf settings
gnome-display-properties definitely overrides xorg.conf settings
Status: RESOLVED DUPLICATE of bug 560827
Product: gnome-control-center
Classification: Core
Component: Display
2.24.x
Other All
: Normal normal
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-08 19:04 UTC by Skippy le Grand Gourou
Modified: 2009-02-26 01:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24



Description Skippy le Grand Gourou 2008-12-08 19:04:42 UTC
Please describe the problem:
I know this is probably a wanted behaviour, but there should be a way to cancel it, for instance a reset button.

Setting the resolution via gnome-display-properties forbids any use of xorg.conf to set correct resolutions. This is particularly painful in conjunction with the bug #562944 ("In multi-screen setting, I cannot choose on which screen the gnome panel should be").

Steps to reproduce:
1. Configure a custom xorg.conf, for instance non-cloned dual-screen.
2. Play a bit with gnome-display-properties.
3. Figure out you cannot do what you want with gnome-display-properties, so come back to xorg.conf.
4. Restart X.


Actual results:
Xorg.conf settings are simply ignored, it is not possible to cancel gnome-display-properties settings if it cannot do what you want.

Expected results:
One should be able to cancel gnome-display-properties settings if it cannot do what one wants.

Does this happen every time?
Yes.

Other information:
This bug is a duplicate of #560827, which I found not explicit enough as it contains two bugs. Sorry for that.
Comment 1 Skippy le Grand Gourou 2008-12-08 19:07:57 UTC
I forgot to post the work-around for people with the same problem : just remove ~/.config/monitors.xml (or ~/.gnome2/monitors.xml).
Comment 2 Federico Mena Quintero 2009-02-26 01:46:10 UTC

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