Bug 174428 - selinux=0 makes firstboot go bang
Summary: selinux=0 makes firstboot go bang
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact:
URL:
Whiteboard:
Depends On: 174722
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-11-28 22:54 UTC by Dave Jones
Modified: 2015-01-04 22:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-02 15:54:52 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.