Bug 705121

Summary: system-config-kickstart --generate filename doesn't work
Product: [Fedora] Fedora Reporter: Lars Bjorndal <lars>
Component: system-config-kickstartAssignee: Chris Lumens <clumens>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 14CC: clumens
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-16 18:02:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Lars Bjorndal 2011-05-16 17:54:21 UTC 
Description of problem:

In Fedora core 9, or something like that, I could use the command
'system-config-kickstart --generate filename.ks' to create a kickstart
file based on the current system settings and set of packages, without
having an X server running. Now, in Fedora 14, it doesn't work.

Version-Release number of selected component (if applicable):
2.8.6.1-1.fc14

How reproducible:
Allways

Steps to Reproduce:
1. Log in to a system that doesn't run X.
2. Run 'system-config-kickstart --generate file.ks'
  
Actual results:

Traceback (most recent call last):
  File "/usr/bin/system-config-kickstart", line 28, in <module>
    from meh.ui.gui import GraphicalIntf
  File "/usr/lib/python2.7/site-packages/meh/ui/gui.py", line 21, in
  <module>
    import gtk
  File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py",
  line 64, in <
module>
    _init()
  File "/usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py",
  line 52, in _
init
    _gtk.init_check()
RuntimeError: could not open display

Expected results:

It should generate a kickstart file.
Comment 1 Chris Lumens 2011-05-16 18:02:39 UTC 

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