Description of problem: sealert often runs for me on my old testbox when I login to the desktop. Today I got a python backtrace in the "sealert Error" dialog, which I attach.
Created attachment 155653 [details] sealert-backtrace.gz
Thanks for reporting this, I could use two more pieces of information 1) What is the package NVR? 2) Does /var/log/setroubleshoot/setroubleshootd.log also have python backtrace's in it and if so could you attach the log file so I could look at it? Thanks
It is setroubleshoot-1.9.4-2.fc7, the version in F7.
Created attachment 155769 [details] setroubleshootd.log Here is the setroubleshootd.log backtrace that seems to keep occurring. My desktop is running in ja_JP.UTF-8 if that helps.
Thank you for taking the time to report this and follow up with the information, it is very helpful. This problem looks to be identical to another recent bug report upstream. I will immediately investigate.
update: The issue is still being researched, we know why the problem occurs, but we don't yet know the best way to address it which will work correctly across various python versions, python extensions (libxml2 & pygtk), and linux distributions, each has their own issues :-( We are working on finding a solution.
*** Bug 243077 has been marked as a duplicate of this bug. ***
I have built ana new RPM (setroubleshoot-1.9.7-1.fc8) in rawhide, I believe this will fix the problems related to setroubleshootd and sealert being unable to communicate when the system language is non-latin. The RPM should show up in rawhide shortly or you may download it here: http://koji.fedoraproject.org/koji/buildinfo?buildID=8705 Please install this and let me know if it resolves the problem, if it does I will push a similar update to F7.
*** Bug 243608 has been marked as a duplicate of this bug. ***
http://koji.fedoraproject.org/koji/buildinfo?buildID=8705 Works for me. Waiting for FC 7 Update package.
setroubleshoot-1.10.1-1.fc7 has been pushed to the Fedora 7 testing repository. If problems still persist, please make note of it in this bug report.