Hide Forgot
Description of problem: It is possible to install setroubleshoot* packages, but none of them requires pygtk2-libglade, which is needed by sealert/setroubleshoot. Version-Release number of selected component (if applicable): setroubleshoot-plugins-2.1.60-1.el6.noarch setroubleshoot-2.2.94-1.el6.ppc64 setroubleshoot-server-2.2.94-1.el6.ppc64 How reproducible: always Steps to Reproduce: # rpm -e pygtk2-libglade # sealert -S Actual results (1 record for each run appears in /var/log/messages): Feb 4 08:46:55 ibm-js24-01 setroubleshoot: [program.ERROR] exception ImportError: No module named glade#012Traceback (most recent call last):#012 File "/usr/bin/sealert", line 988, in <module>#012 run_app(username)#012 File "/usr/bin/sealert", line 86, in run_app#012 app = SEAlert(user)#012 File "/usr/bin/sealert", line 600, in __init__#012 from setroubleshoot.browser import BrowserApplet#012 File "/usr/lib64/python2.6/site-packages/setroubleshoot/browser.py", line 18, in <module>#012 import gtk.glade#012ImportError: No module named glade Expected results: no tracebacks in /var/log/messages
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Lets fix this in 6.2.
Fixed in setroubleshoot-3.0.31-1.el6
Clearing qa_ack, setroubleshoot has been removed from 6.2 approved list.
+Requires: pygtk2-libglade needs to be added.
Fixed in setroubleshoot-3.0.38-2.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1509.html