Bug 695288

Summary: [abrt] policycoreutils-gui-2.0.83-19.1.el6: __init__.py:49:seinfo:RuntimeError: No default policy found.
Product: Red Hat Enterprise Linux 6 Reporter: Yogesh <ychavan>
Component: policycoreutilsAssignee: Daniel Walsh <dwalsh>
Status: CLOSED ERRATA QA Contact: Milos Malik <mmalik>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: dwalsh, mmalik, vgaikwad
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 15:30:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Yogesh 2011-04-11 10:32:34 UTC 
Description of problem:
When selinux is disabled, policycoreutils-gui crashes with error
__init__.py:49:seinfo:RuntimeError: No default policy found.


Version-Release number of selected component (if applicable):
abrt version: 1.1.13
architecture: x86_64
cmdline: /usr/bin/python -Es /usr/share/system-config-selinux/polgengui.py
component: policycoreutils
executable: /usr/share/system-config-selinux/polgengui.py
kernel: 2.6.32-71.18.2.el6.x86_64
package: policycoreutils-gui-2.0.83-19.1.el6
reason: __init__.py:49:seinfo:RuntimeError: No default policy found.
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
time: 1300572024
uid: 0 

How reproducible:
Always

Steps to Reproduce:
1. Disable selinux
2. run command policycoreutils-gui

  
Actual results:
You get python crash message

Expected results:
It should provide proper GUI messagebox that selinux is disabled OR it should allow to generate offline selinux policy.


Additional info:
Reported and solved in F14
https://bugzilla.redhat.com/show_bug.cgi?id=632191
Comment 1 Daniel Walsh 2011-05-26 14:18:57 UTC 
Fixed in policycoreutils-2.0.83-19.2
Comment 5 errata-xmlrpc 2011-12-06 15:30:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1637.html