Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 118060

Summary: during firstboot X settings are not saved
Product: [Fedora] Fedora Reporter: Armijn Hemel <armijn>
Component: firstbootAssignee: Brent Fox <bfox>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 19:01:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Armijn Hemel 2004-03-11 15:51:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)
Gecko/20031114

Description of problem:
During firstboot when installing Fedora Core 2 test 1 the settings for
the X server are not saved it seems. I chose 1280x1024, but when X
starts I get 1024x768 instead. I tried again with a fresh reinstall
and chose 800x600 instead, but I get 1024x768. The monitor is a Dell
1800FP, which cannot be probed by ddcprobe. This might be a part of
the problem (maybe with other monitors it never shows up, because they
do get probed correctly).

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


How reproducible:
Always

Steps to Reproduce:
1.install FC2 test 1
2.change X config from default 1024x768 to another resolution in firstboot
3.
    

Actual Results:  Nothing! It stayed at 1024x768

Expected Results:  The resolution should have changed.

Additional info:

Comment 1 Brent Fox 2004-03-11 17:12:38 UTC

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

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