Bug 438791

Summary: firstboot should not create xorg.conf for Live instances
Product: [Fedora] Fedora Reporter: Jens Petersen <petersen>
Component: LiveCDAssignee: Jeremy Katz <katzj>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-04-01 16:24:44 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:
Bug Depends On:    
Bug Blocks: 235706    

Description Jens Petersen 2008-03-25 09:27:32 UTC 
Description of problem:
Live instances of Fedora get a xorg.conf generated (presumably
by firstboot?).  Now that we have a persistence option for Live
images on USB it would be better not to create the xorg.conf file
since the persistent image may be booted on a different machine
with different graphics chipset, etc.

Steps to Reproduce:
1. # livecd-tools-iso-to-disk --overlay-size-md 512 ...
2. boot live image on computer A
3. later use live image on computer B with different graphics hardware
  
Actual results:
3. X doesn't start because wrong driver loaded.

Expected results:
3. no xorg.conf file so that it starts on any computer

Additional info:
Workaround is to delete xorg,conf after 2.
Comment 1 Jeremy Katz 2008-03-25 13:34:22 UTC 
firstboot doesn't do this, it's the livecd init script.  And there's one or two
things I need to double check with ajax this week before changing this
Comment 2 Jeremy Katz 2008-04-01 16:24:44 UTC 
Changed this last week.
Comment 3 Jens Petersen 2008-04-04 09:32:36 UTC 
Now it runs system-config-display?
Comment 4 Jeremy Katz 2008-04-04 13:33:06 UTC 
The firstboot initscript had changed its logic -- Chris fixed this yesterday
after I finally figured out what was launching it.