Hi, Le 24/05/2011 19:01, Christoph Goehre a écrit : > Hi, > > just run icedove in safe-mode (icedove -safe-mode) to eliminate a > extension problem. If it crash again, consider to move .icedove into > .icedove.old.
Yes. Safe mode doesn't work, same problem. Removing the parameters from the mail counter and restarting afresh (moving the .icedove folder) resolves the segfault issue but renders icedove half useless for me because I heavily rely on my mail archives for my professional life :) Nonetheless, even by starting afresh, it segfaults instantly when I ask to import the parameters from my netscape4 acount. > Could you generate backtrace output with 'thread apply all bt full'? I'll do that soon, but before, I can update some information. > And last but not least downgrade to icedove 3.0.11-1+squeeze1[1], check > it, update to 3.0.11-1+squeeze2 and check again. I already downgrade yesterday, as I was quite desesperate. Well, the old icedove segfaults the same way. In fact, it segfault while trying to index my Sent mail folder inherited from 10 years ago, with more than 5000 messages. So may be related to the size, or the content of my sent mail folder and, anyway, not related to the security update. May be it doesn't help neither that my mail archive is situated on a remote machine, mounted throught sshfs (the remote machine is a secured and backuped system contrary to the local computer). Full backtrace soon. Thanks for the tips. Stéphane -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
