Bug 924923

Summary: [abrt] setroubleshoot-server-3.2.3-1.fc18: __init__.py:156:<module>:ValueError: Failed to read /sys/fs/selinux/policy policy file
Product: [Fedora] Fedora Reporter: Alexander230 <fire_2005>
Component: setroubleshootAssignee: Daniel Walsh <dwalsh>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dwalsh, mgrepl, rogeliolt
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:a90cf98239f98e95940e5acfce1d507ebafce2e1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-24 19:33:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ
none
File: smolt_data none

Description Alexander230 2013-03-22 20:10:12 UTC 
Description of problem:
This error appears after every reboot

Version-Release number of selected component:
setroubleshoot-server-3.2.3-1.fc18

Additional info:
cmdline:        /usr/bin/python -Es /usr/sbin/setroubleshootd -f ''
dso_list:       policycoreutils-python-2.1.13-56.fc18.i686
executable:     /usr/sbin/setroubleshootd
kernel:         3.8.3-203.fc18.i686
uid:            0
Comment 1 Alexander230 2013-03-22 20:10:15 UTC 
Created attachment 714754 [details]
File: backtrace
Comment 2 Alexander230 2013-03-22 20:10:18 UTC 
Created attachment 714756 [details]
File: core_backtrace
Comment 3 Alexander230 2013-03-22 20:10:21 UTC 
Created attachment 714758 [details]
File: environ
Comment 4 Alexander230 2013-03-22 20:10:23 UTC 
Created attachment 714759 [details]
File: smolt_data
Comment 5 Miroslav Grepl 2013-03-25 07:07:39 UTC 
Is this on a system with disabled SELinux?
Comment 6 Daniel Walsh 2013-04-24 19:33:29 UTC 
I think this was fixed by a policycoreutils update.