Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 161507 - Changing resolution reverts changes to xorg.conf to default (bad!)
Changing resolution reverts changes to xorg.conf to default (bad!)
Product: Fedora
Classification: Fedora
Component: system-config-display (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
Depends On:
  Show dependency treegraph
Reported: 2005-06-23 15:43 EDT by Michael Lee Yohe
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-30 19:12:47 EST
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 Michael Lee Yohe 2005-06-23 15:43:14 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
I'm having difficulties with the default xorg-x11 configuration with Fedora Core 4 (see Bug 161495).  Mike Harris suggested disabling "dri" in the configuration file to correct.  It did.

However, when I ran system-config-display to change resolution, it put back "dri" as a part of the modules to be loaded in X - reintroducing my original problem.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Comment out a module in xorg.conf.
2. Run system-config-display - change something - save.
3. Open xorg.conf.

Actual Results:  Commented out portions are added back to the configuration file.

Expected Results:  system-config-display should honor the comments and leave them out!

Additional info:
Comment 1 Adam Jackson 2006-10-30 19:12:47 EST
Should no longer be doing this in FC6.  Please reopen if this is still an issue
for you.

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