Bug 442869 - /usr/share/system-config-display/xconf.py does not change monitor settings
/usr/share/system-config-display/xconf.py does not change monitor settings
Status: CLOSED DUPLICATE of bug 234131
Product: Fedora
Classification: Fedora
Component: system-config-display (Show other bugs)
i686 Linux
low Severity low
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-04-17 06:10 EDT by David Tonhofer
Modified: 2018-04-11 14:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-17 11:23:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description David Tonhofer 2008-04-17 06:10:22 EDT
Description of problem:

Under KDE:

Monitor settings in xorg.conf are as follows:

Section "Monitor"
        Identifier   "Monitor0"
        ModelName    "LCD Panel 1280x1024"
        HorizSync    31.5 - 64.0
        VertRefresh  56.0 - 65.0
        Option      "dpms"

I want to change them to a higher resolution (which the Video Card may not
support), in this case 1680x1050.

Select Hardware > Monitor > LCD_Panel_1680x1050; OK; OK

A dialog says "Display settings changed ... configuration was written to
/etc/X11/xorg.conf, original configuration saved as /etc/X11/xorg.conf.backup"

The xorg.conf file has indeed been written (judging from its modify time) but
its contents have not changed. No xorg.conf.backup has been created.

This also happens if I want to change the LCD panel to a lower resolution. 

so I run xconf.py either from the KDE system menu or from the command line.
Comment 1 Vasile Chelban 2008-04-17 07:08:15 EDT
that's actually long standing bug in rxpxl code.
See bug #234131
Comment 2 Matěj Cepl 2008-04-17 11:23:37 EDT

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

Note You need to log in before you can comment on or make changes to this bug.