Bug#522162: reassign 522162 to libglib2.0-0

Ludovic Aubry ludovic.aubry at logilab.fr
Fri Apr 10 10:34:49 UTC 2009


On Thursday 09 April 2009 15:21:25 Josselin Mouette wrote:
> Le jeudi 09 avril 2009 à 15:02 +0200, Ludovic Aubry a écrit :
> > reassign 522162 libglib2.0-0 2.16.6-1+lenny1
>
> Do you have a backtrace of the crash, at least with glib debugging
> symbols?
>
> Does it also happen with 2.16.6-1 or is it a regression in the
> proposed-updates package?

Well, I downgraded to 2.16.6-1+lenny1 and 2.16.6-1 and couldn't
reproduce the problem with either version.

I also tried downgrading libpcre3 since a newer version from testing
had been pulled in.

I also checked if anything special was done on this machine since yesterday
but not much happened : some old (probably unrelated) packages were purged
(python2.2, python2.4 some old kernel packages...)

Unfortunately I haven't kept the backtrace I got with gdb. there was no 
debugging symbol available, and the only and last symbol visible was
g_static_private_set which is probably not that useful...

I'll tag this bug unreproducible since I can't even reproduce my own bug.

regards,






More information about the pkg-gnome-maintainers mailing list