Description of problem: Under the circumstances described in bug #229283, setroubleshoot fails to start on boot and displays a traceback on the console. Version-Release number of selected component (if applicable): setroubleshoot-1.7.1-1.fc6 How reproducible: always Steps to Reproduce: 1. chcon -t rpm_script_tmp_t /etc/services 2. service syslog restart 3. setroubleshootd Actual results: Expected results: Additional info:
Created attachment 148374 [details] Python traceback
cleaning out old bugs. This was fixed a while ago, not sure about the FC-6 version, but in current versions all that happens is this is written to stderr: exception when creating syslog handler: (2, 'No such file or directory') and then everything continues normally. So I'm going to close this out, I'd close it as CURRENT RELEASE except it was fixed so long ago I don't know the version number so I'm just closing it RAWHIDE.