On Sun, Aug 20, 2006 at 08:53:27AM +0200, Mike Hommey <[EMAIL PROTECTED]> wrote: > On Sun, Aug 20, 2006 at 02:34:47AM +0200, Alexander Sack <[EMAIL PROTECTED]> > wrote: > > > > Mike, can you take a look? Appears to be related with xulrunner > > transition. So maybe you have an idea what the reason might be. > > I didn't try to reproduce the bug and see the backtrace to verify my > assumptions, but I think it is the same bug as #376323, which I wanted > to fix in next upload of xulrunner at the time I wrote to the bug but > with the security update of 1.8.0.5, I forgot to apply the patches from > the BTS. It will be fixed in 1.8.0.5-2 anyway. I'm just waiting for > 1.8.0.5-1 to migrate to testing. > > I'll take a look at kazehakase to see if it's the same bug.
Mmmmm, sadly, i can't even reproduce the bug. Is the password manager enabled by default ? I see kazehakase has indeed a user profile for the underlying gecko, which means it may not be #376323, but i'd like to at least be able to reproduce the bug... Gerfried, could you provide detailed steps to be able to reproduce for a non kazehakase user (meaning with no $HOME/.kazehakase) in the first place ? Alternatively, it would be nice to have a full backtrace after segfault (preferably install libxul0d-dbg before getting the backtrace). Maybe an strace would be helpful, too. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
