Bug 174428

Summary:	selinux=0 makes firstboot go bang
Product:	[Fedora] Fedora	Reporter:	Dave Jones <davej>
Component:	system-config-securitylevel	Assignee:	Chris Lumens <clumens>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	pfrields
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:	2005-12-02 15:54: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:
Bug Depends On:	174722
Bug Blocks:

Description Dave Jones 2005-11-28 22:54:23 UTC

had to install with selinux=0 due to broken policy in todays rawhide.
On reboot, firstboot started up, and then went..

Traceback (most recent call last):
  File "/usr/share/firstboot/firstbootWindow.py", line 290, in nextClicked
    result = module.apply(self.notebook)
  File "/usr/share/firstboot/modules/firstboot_selinux.py", line 75, in apply
    if self.selinuxPage.apply() == 1:
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line 366, in apply
    type=self.getType()
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line 358, in getType
    return self.types[self.selinuxTypeOptionMenu.get_active()]
IndexError: list index out of range

Comment 1 Chris Lumens 2005-12-01 17:50:47 UTC

No policy packages are getting installed (see bug I just marked as a
dependancy).  We should probably do something smarter if there aren't any
installed, though.