Hide Forgot
Description of problem: I'm not sure exactly what's going on, but here's my problem. I only get AVC denial messages in /var/log/messages and setroubleshoot isn't working. When I run 'semodule DB' I get: 'libsemanage.semanage_fc_sort: WARNING: semanage_fc_sort: Incomplete context.' and new AVC denials don't show using 'ausearch -m avc -ts recent' or 'grep AVC /var/log/audit/audit.log | sedispatch'. Version-Release number of selected component (if applicable): selinux-policy-targeted-3.10.0-11.fc17 How reproducible: Everytime Steps to Reproduce: 1.Get an AVC denial with SELinux set to enforcing, and program closes 2.setroubleshoot shows nothing wrong 3.Program runs fine with SELinux set to permissive Actual results: No AVC denial message with setroubleshoot Expected results: setroubleshoot shows what SELinux just blocked Additional info:
This is happening to me in Fedora 16. Programs well known to have problems with SELinux auto close or have malfunctions, but SELinux troubleshooter does not notify in taskbar. I have KDE 4.7.3. Tom could you change version to Fedora 16? I think it could be better
The problem is on update auditd is not running. systemctl enable auditd systemctl start auditd Then the auditd will start sending avc's to setroubleshoot.
[root@computer ]# systemctl enable auditd Failed to issue method call: Invalid argument
systemctl enable auditd.service systemctl start auditd.service should work.
Oops always forget the .service part.
Why did you close as not a bug? The system did not show SELinux errors until we do systemctl enable auditd.service systemctl start auditd.service That's not normal
Well I guess I should have closed it as cantfix, since updates from F15 to F16 did not maintain the state of running services. I am not sure why this decision was made, but that is what caused the problem. Nothing audit, setroubleshoot or selinux can do about it.
I don't understand well these technical things, but we must let know developer leaders that SELinux troubleshooter is no longer working, and this is not admissable.
Yes I understand. On fresh installs it will work, but on updates no system services that were working before work afterwards.
Then someone should put systemctl enable auditd.service systemctl start auditd.service under upgrade FAQs from Fedora 15 to Fedora 16
Bill who should I ping to do this?
It's on the wiki - https://fedoraproject.org/wiki/Common_F16_bugs
Maybe we should call this out on setroubleshoot directly.