Bug 174428 - selinux=0 makes firstboot go bang
selinux=0 makes firstboot go bang
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Depends On: 174722
  Show dependency treegraph
Reported: 2005-11-28 17:54 EST by Dave Jones
Modified: 2015-01-04 17:23 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-02 10:54:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dave Jones 2005-11-28 17:54:23 EST
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
  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 12:50:47 EST
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.