Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 140507 - system-config-securitylevel crashes at startup
system-config-securitylevel crashes at startup
Status: CLOSED DUPLICATE of bug 139155
Product: Fedora
Classification: Fedora
Component: system-config-securitylevel (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Paul Nasrat
Depends On:
  Show dependency treegraph
Reported: 2004-11-23 02:24 EST by Michael Opdenacker
Modified: 2007-11-30 17:10 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:07:14 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 Michael Opdenacker 2004-11-23 02:24:56 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)

Description of problem:

I noticied I never managed to start the dialog to set the security
level from the desktop menus.

Here's what happens when I start system-config-security level from a
root shell:

> system-config-securitylevel
Traceback (most recent call last):
18, in ?
  File "/usr/share/system-config-securitylevel/securitylevel.py", line
427, in stand_alone
    self.selinuxPage = selinuxPage.selinuxPage()
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line
329, in __init__
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line
427, in refreshTunables
  File "/usr/share/system-config-securitylevel/selinuxPage.py", line
418, in loadBooleans
IndexError: list index out of range

Note that after the installation process, which let me choose a
security level (I don't remember which one I chose), I never fiddled
with the security level settings. This is the first time I am trying
to set this parameter.

Anybody else facing this issue?



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

How reproducible:

Steps to Reproduce:
1. Start system-config-securitylevel

Actual Results:  See a nice Python error stack trace.

Expected Results:  The System Security Level dialog should have been

Additional info:
Comment 1 Emmanuel Viennet 2004-11-23 05:06:59 EST
I observe exactly the same problem.

So many bugs in FC3 !

Comment 2 Michael Opdenacker 2004-11-23 05:13:32 EST
Thank you Emmanuel for your experience.

However, I find you a little bit hard on FC3. At least on my side, it
worked flawlessly, with just a few exceptions.

From my experience, most issues will be addressed pretty quickly by
Fedora Core / Red Hat developers.


Comment 3 Bradley 2004-11-23 07:40:21 EST
I did an FC2->FC3 upgrade. system-config-securitylevel did start, but once I
enabled selinux and relabeled, I ran into this bug.
Comment 4 Paul Nasrat 2004-11-23 08:43:36 EST
Duplicate of 139155

*** This bug has been marked as a duplicate of 139155 ***
Comment 5 Red Hat Bugzilla 2006-02-21 14:07:14 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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