On Wed, Mar 25, 2009 at 02:33:44PM +0530, Ritesh Raj Sarraf wrote: > Hi Pierre, > > This bug is more than a month old. > > If you're busy, is it okay if I NMU it ? >
Hi, 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. Regards, Pierre [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515135 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
