On Wed, 09 Feb 2011 16:37:13 +0100 Antonio Ospite <osp...@studenti.unina.it> wrote:
[...] > I am still getting it on 3.1.0-1. > > I haven't figured out what triggers it but I've got it a couple of a > times in a day. > > Attached there is my backtrace log, I'll try to supply a log with > "thread apply all bt" the next time I hit it, if needed. > Here is the "thread apply all bt full" log attached. The problem happened once again to me after downloading some messages via POP3 (once at message 4/5 once at message 2/3), I am not sure if sylpheed lost any message on crash, I'll take care to look at that the next time it happens. Thanks, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
sylpheed-3.1.0-crash-backtrace-threads.log
Description: Binary data
pgp5olhhHnWna.pgp
Description: PGP signature
