Description of problem: In logs I see many lines like: Oct 22 09:57:24 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:24 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:24 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:24 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:25 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:25 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:25 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:26 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:26 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 Oct 22 09:57:26 hubbitus setroubleshoot: SELinux запрещает /opt/google/chrome/chrome доступ «read» к /etc/localtime. For complete SELinux messages. run sealert -l 7207486f-2c19-4d94-822c-4e96aa6c8204 When I run suggested "sealert -l 7207486f-2c19-4d94-822c-4e96aa6c820" got error: query_alerts error (1003): id (7207486f-2c19-4d94-822c-4e96aa6c8204) not found And in logs appeared additional message: Oct 22 10:56:16 hubbitus setroubleshoot: [xml.ERROR] read_xml_file() libxml2.parserError: xmlParseFile() failed Oct 22 10:56:16 hubbitus sedispatch: AVC Message for setroubleshoot, dropping message Version-Release number of selected component (if applicable): $ rpm -qf `which sealert` setroubleshoot-server-2.2.102-1.fc14.i686 How reproducible: Always
Did you delete alerts in SELinux Troubleshooter? It looks so.
In KDE appeared applet icon about new denied, I click on it, but also appeared message what no new alerts. I think it is because the same error.
setroubleshoot-3.0.15-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/setroubleshoot-3.0.15-1.fc14
setroubleshoot-plugins-3.0.8-1.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/setroubleshoot-plugins-3.0.8-1.fc14
setroubleshoot-3.0.15-1.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update setroubleshoot'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/setroubleshoot-3.0.15-1.fc14
setroubleshoot-plugins-3.0.8-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
setroubleshoot-3.0.15-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.