Description of problem:
Cannot start SELinux Troubleshooter after updates.

Version-Release number of selected component (if applicable):
Not sure which rpm is causing the problem.  See link at bottom.

selinux-policy-targeted-3.9.16-30.fc15        Fri 24 Jun 2011 09:53:25 PM MDT
selinux-policy-3.9.16-30.fc15                 Fri 24 Jun 2011 09:51:59 PM MDT
libselinux-python-2.0.99-4.fc15               Fri 24 Jun 2011 08:10:44 PM MDT
libselinux-utils-2.0.99-4.fc15                Fri 24 Jun 2011 08:09:32 PM MDT
libselinux-2.0.99-4.fc15                      Fri 24 Jun 2011 08:08:52 PM MDT


How reproducible:
After updating SELinux cannot start SELinux Troubleshooter.  Get following error:
Opps, sealert hit an error!

Traceback (most recent call last):
  File "/usr/bin/sealert", line 692, in <module>
    run_as_dbus_service(username)
  File "/usr/bin/sealert", line 112, in run_as_dbus_service
    app = SEAlert(user, dbus_service.presentation_manager, watch_setroubleshootd=True)
  File "/usr/bin/sealert", line 326, in __init__
    from setroubleshoot.browser import BrowserApplet
  File "/usr/lib64/python2.7/site-packages/setroubleshoot/browser.py", line 46, in <module>
    import report.io.GTKIO
ImportError: No module named GTKIO

Steps to Reproduce:
1. Either from getting an SELinux alert or by trying to start SELinux troubleshooter.
2.
3.
  
Actual results:
SELinux Troubleshooter will not start and only gives an error message.

Expected results:
SELinux to run.

Additional info:
Temporary solution posted by pavelmialko:
http://pavelmialko.livejournal.com/616.html