On Tue, Aug 26, 2008 at 3:37 PM, Matsche <[EMAIL PROTECTED]> wrote: > Alexander Toresson wrote: >> >> Could this be caused by http://bugs.debian.org/496125 , perhaps? You >> could try downgrading libxml2 and libxml2-dev again, or upgrading to >> the new -3 (which unfortunately doesn't seem to have reached lenny >> yet). >> >> // Alexander >> > > Maybe, but i'm bewildered about the fact, that such e bug can pass the > "quality control" at that state. > I've thought lenny is in frozen state. > This is a realy serious bug in a very fundamental lib. > > matsche >
I still think this should be the problem. You could try downgrading/upgrading libxml2, or getting a backtrace using gdb (if so, please have the -dbg package for libxml2 installed). Also, please reply to the bts, and not just to me. // Alexander -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
