I have the exact same error, however when I check the System Tools - >Systems Logs SELinux appears to load without any problems. I still can't believe that no-one else has this problem, it appeared after the last SELinux update. Paul Davis