Bug 136873

Summary: system-config-display doesn't read driver from xorg.conf
Product: Red Hat Enterprise Linux 4 Reporter: John A. Hull <john_hull>
Component: system-config-displayAssignee: Paul Nasrat <pnasrat>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0CC: amit_bhutani
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:06:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description John A. Hull 2004-10-22 19:39:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When starting system-config-display, it probes the video card and 
then automatically chooses a driver based on the card type. This is a 
problem when using the closed-source nvidia or ati drivers, because 
it will automatically replace that driver with an open-source driver. 
This prevents users from starting system-config-display and using it 
to configure their monitor and resolutions only, since it will change 
their X driver to something else. 

redhat-config-display was more useful in this regard, since it would 
change the driver only if the user chose to probe or pick a new video 
card. If would be useful if this functionality was included is some 
form in system-config-display also. 

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

How reproducible:

Steps to Reproduce:
1. Set the video driver in xorg.conf for an nvidia card from "nv" 
to "nvidia"
2. Start system-config-display
3. Press "OK"
4. Look in xorg.conf. Driver has changed back to nv

Expected Results:  system-config-display should not change the driver 
used unless explicitly told to do so. 

Additional info:

Comment 1 Paul Nasrat 2004-10-23 09:55:49 UTC
Already fixed in rawhide

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:06:34 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.