Bug 130571
| Summary: | Can't read kickstart files | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Johan Dahl <johan.dahl> |
| Component: | system-config-kickstart | Assignee: | Paul Nasrat <nobody+pnasrat> |
| Status: | CLOSED RAWHIDE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | ||
| 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: | 2004-08-25 10:06:52 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: | |||
Could you test with system-config-kickstart from rawhide these fixes should be there already. system-config-kickstart-2.5.12-3 Now I can open saved kickstart files both as a command line argument and from inside the program. Very good! |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Description of problem: Then I run: $ system-config-kickstart ks.cfg on an previously created kickstartfile I get this message. If uses "Open" in "File"-menu it also happens. Traceback (most recent call last): File "/usr/share/system-config-kickstart/system-config-kickstart.py", line 81, in ? kickstartGui.kickstartGui(file) File "/usr/share/system-config-kickstart/kickstartGui.py", line 164, in __init__ self.fillData() File "/usr/share/system-config-kickstart/kickstartGui.py", line 307, in fillData self.firewall_class.fillData() File "/usr/share/system-config-kickstart/firewall.py", line 221, in fillData self.firewallCustomizeRadio.set_active(gtk.TRUE) AttributeError: 'NoneType' object has no attribute 'set_active' Version-Release number of selected component (if applicable): 2.5.11-1 How reproducible: Always Steps to Reproduce: 1. run "system-config-ks.cfg" in terminal 2. 3. Actual Results: Error messages and the program doesn't come up. Expected Results: The program should have started and allowed me to continue editing the kickstart file. Additional info: