Bug 829024
| Summary: | [abrt] setroubleshoot-server-3.1.11-1.fc17: __init__.py:49:seinfo:RuntimeError: No default policy found. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | totophe56 <christophe.ribet> |
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | dwalsh, geoffleach.gl, ifd2000, jan.public, kosmas, mgrepl, midnightsteel |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:6fe87bbb0e03f62de086f9a6895bb633f8615be6 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-08-01 18:42:06 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: | |||
|
Description
totophe56
2012-06-05 19:33:02 UTC
Did you run this command on a machine without the selinux-policy-targeted package installed? no the linux policy was targeted i mised install tklib the trouble is solved thanks Will be fixed to not crash if selinux-policy is not installed in setroubleshoot-3.1.12. Unable to authorise any admin action from GUI after I have to disable SELinux that denies me to do these things Package: setroubleshoot-server-3.1.9-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) 0. All recomendations from SELinux troubleshoot have being applied 1. SELinux prevents me to mount local drives 2. SELinux policy have being upgraded to 128 yum update --enablerepo=updates-testing selinux-policy-3.10.0-128.fc17 3. Reboot 4. SELinux continue to protect me from my local filesystems 5. SELinux disabled through /etc/selinux/conf 6. Reboot 7. SELinux continue to protect me from my local filesystems 8. Unable to see new solution from SELinux troubleshoot (see Comment #4) If SELinux is disabled it is not preventing you from doing anything. Why are you adding to this bugzilla. If you have a support issue please ask on the mailing list or irc. You could boot the kernel with selinux=0 option to make sure it is disabled. I'm sorry. I just followed the standard procedure. I will try to avoid this action in the future. I have used RedHat since 1995 and before SELinux become an integral part of the system I have not experienced problems when changing release. I would really like that it was disappeared, but unfortunatelly, it's not possible. I am not sure what standard procedure you are talking about. If you want to disable SELinux on a fresh install you can do this in a kickstart. You can add selinux=0 to the grub entry of the kernel or disable selinux in /etc/selinux/config. If you want SELinux turned off you probably do not even want setroubleshoot installed yum remove setroubleshoot Standard procedure is to press a "Report bug" button. Thanks for Your time. Now I'm sure - the best way to avoid problems with SELinux is to turn SELinux off after an upgrade. I will do it today. But,for now, I'm not sure that problem is inside SELinux - it also can be inside GNOME/KDE or security wrapper using them to confirm rights for mounting filesystems or confirming keys for packages during system update. Fresh install does not have this problem, but it completelly destroys my data. As I understand SELinux Troubeshooter just indicate problems that have created lately. So removing SELinux Troubeshooter - is to break the red light instead of to solve the problem, which leads to its blinking. Alexey if you want to talk about what SELinux is reporting, then fine I will help you fix them, If you come in and say SELinux sucks, I turn it off, then I say fine. Once you turn SELinux off, remove these packages and if you have other problems go to fedora-list for help, or report bugs on other parts of the system. SELinux Troubleshooter is not going to report problems on an SELinux disabled system. selinux is disabled. settings same as f16 Package: setroubleshoot-server-3.1.11-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) I have removed the setroubleshoot package. I'll report back on the results. BTW, I'm not trying to debug selinux problems; just being a good user (IMHO) by reporting problems that are reported by abrt. Removal of setroubleshoot did not change the problem. I won't report duplicates (one per day) unless requested. Just catching up on this, but could you report what you are still seeing? yum remove setroubleshoot-server Hmmm ... didn't I do this already? Oh well .... #yum remove setroubleshoot-server problem solved. Guess I didn't run that before. Thanks. Tried to start SELinux Troubleshoot. Package: setroubleshoot-server-3.1.12-1.fc17 Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) Did you try "yum remove setroubleshoot-server"? I had no selinux policy installed. yum install selinux-policy-targeted solved the issue. This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |