Description of problem: From /var/log/setroubleshoot/setroubleshootd.log: 2009-06-28 16:14:56,237 [plugin.ERROR] failed to load bind_ports plugin Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/setroubleshoot/util.py", line 428, in load_plugins mod = imp.load_module(module_name, mod_fp, mod_path, mod_description) File "/usr/share/setroubleshoot/plugins/bind_ports.py", line 24, in <module> from sesearch import * ImportError: No module named sesearch 2009-06-28 16:14:56,251 [plugin.ERROR] failed to load default plugin Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/setroubleshoot/util.py", line 428, in load_plugins mod = imp.load_module(module_name, mod_fp, mod_path, mod_description) File "/usr/share/setroubleshoot/plugins/default.py", line 24, in <module> from sesearch import * ImportError: No module named sesearch 2009-06-28 16:14:56,254 [plugin.ERROR] failed to load restorecon plugin Traceback (most recent call last): Version-Release number of selected component (if applicable): setroubleshoot-server-2.2.9-1.fc12.x86_64 setroubleshoot-plugins-2.1.3-1.fc12.noarch setroubleshoot-2.2.9-1.fc12.x86_64 How reproducible: always Steps to Reproduce: 1. start setroubleshootd
Wrong component, sorry.
This bug has been resolved in the latest version, 2.2.10. We moved sesearch into the setroubleshoot package but failed to update the import statements in the plugins that used it.