Rawhide 2007-04-18, system-config-kickstart-2.7.4-1.fc7
If you run system-config-kickstart, you get a traceback as follows:
Summary: TBefdff07c selinuxPage.py:75:__init__:AttributeError: 'NoneType' object
has no attribute 'set_model'
Traceback (most recent call last):
File "/usr/bin/system-config-kickstart", line 81, in <module>
File "/usr/share/system-config-kickstart/kickstartGui.py", line 165, in __init__
self.firewall_class = firewall.Firewall(xml, self.ksHandler)
File "/usr/share/system-config-kickstart/firewall.py", line 99, in __init__
self.selinuxWindow = selinuxWindow(selinuxXml)
File "/usr/share/system-config-kickstart/firewall.py", line 40, in __init__
selinuxPage.__init__(self, xml, doDebug, inFirstboot)
File "/usr/share/system-config-securitylevel/selinuxPage.py", line 75, in __init__
AttributeError: 'NoneType' object has no attribute 'set_model'
Local variables in innermost frame:
xml: <glade.XML object (PyGladeXML) at 0x921c0cc>
listStore: <gtk.ListStore object (GtkListStore) at 0x981da04>
self: <firewall.selinuxWindow instance at 0x981e08c>
What version of system-config-securitylevel do you have installed?
*** Bug 237205 has been marked as a duplicate of this bug. ***
twoerner - both firstboot and system-config-kickstart rely on the screens
provided by system-config-securitylevel. One thing they both need is the
SELinux tab, which is provided to these other programs by the selinuxPage module
in s-c-sl. If you could please add this tab back for F7 so we don't have to
change both firstboot and s-c-ks, that'd be helpful. We can then sort out what
to do permanently after the release.
Look for me in IRC if you have any questions about this.
Please close - this is a duplicate of #234006
This has been fixed by downgrading s-c-securitylevel to 1.7.0 in the F7 tree.
Is there a way we can have people tracking rawhide get the older s-c-sl in a yum
There's no way to fix that short of building a new s-c-sl with a higher epoch
(kind of a gross fix), or one with a version number higher than 1.8.0.
Otherwise people will have to fix this manually.
*** Bug 238746 has been marked as a duplicate of this bug. ***