Bug 187701 - can't modify security level , list index out of range
can't modify security level , list index out of range
Status: CLOSED DUPLICATE of bug 186554
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Depends On:
  Show dependency treegraph
Reported: 2006-04-02 19:48 EDT by Sergio Monteiro Basto
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-04-03 09:38:47 EDT
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 Sergio Monteiro Basto 2006-04-02 19:48:36 EDT
Description of problem:
can't modify any option in system-config-securitylevel because when press ok
give me one python error : list index out of range

Version-Release number of selected component (if applicable):

How reproducible:
 upgrade from FC4 to FC5 in text mode 

Steps to Reproduce:
2.press ok 

Actual results:
Traceback (most recent call last):
  File "/usr/share/system-config-securitylevel/securitylevel.py", line 240, in
    rc = self.apply()
  File "/usr/share/system-config-securitylevel/securitylevel.py", line 402, in apply
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line 379, in apply
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line 371, in getType
    return self.types[self.selinuxTypeOptionMenu.get_active()]
IndexError: list index out of range

Expected results:
modify security level

Additional info:
Comment 1 Sergio Monteiro Basto 2006-04-02 20:17:31 EDT
Install selinux-policy and selinux-policy-targeted is the solution.
Maybe system-config-securitylevel should depend on selinux-policy-targeted
Comment 2 Chris Lumens 2006-04-03 09:38:47 EDT

*** This bug has been marked as a duplicate of 186554 ***

Note You need to log in before you can comment on or make changes to this bug.