On Wednesday 25 Mar 2009 14:45:28 Pierre Chifflier wrote: > Sorry for the late reply ... Actually, I was trying to solve this problem > along with the KeyboardInterrupt [1] one, but the latter appears to be more > complicated than I thought. (I should have set the 'pending' tag ..). > > The cause of the problem seems to be a signal (SIGALRM) received by the > Python code. Unfortunaly, Python is a bit stupid and sends a > KeyboardInterrupt where the problem is really a signal .. > I have contacted setroubleshoot upstream, but so far we haven't found > why this signal is sent (we suspect glib internals, like timers, though > it does not explain why the Python code receives it. > > So the other bugs will be fixed in the next upload, which I can't do > because the new version does not work at all :/ > If you are willing to help, I can provide the new packages, help would > be appreciated.
Yes, it is a tough one. :-( Currently, on my setup, on SELinux violations, I do see the notification in the system tray, but then when I click on it, the browser doesn't open. I have been trying to look at all possible places to figure out why this is happening, but no luck yet. I'll keep trying to see if I can provide more info on both the issues. Thank you. Ritesh -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com "Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part.
