GNOME Bugzilla – Bug 748448
Evolution crashes during usage or whilst not interacting with application
Last modified: 2015-04-28 10:51:41 UTC
Hi, I'm getting this bug in Evolution 3.12.9, on Debian Jessie - and using the KDE Desktop (I haven't checked whether the bug exists when I use other desktops). I also think it might be related to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=360128 . But I can't reopen that. Basically, Evolution is crashing...It has several times crashed whilst I've been using the application, but it also crashes in the background - e.g. if I've been using another program and the Evolution window is open in the background or in the other window. On my laptop this is pretty reproducible - if I leave the program open it will crash within about an hour, maybe less. Happy to try and get a backtrace but someone will have to talk me through it; I tried to look it up but didn't really understand the commands suggested. I tried: CAMEL_DEBUG=all evolution yesterday and got a lot of output but a fair amount of it contained my personal information, emails etc so don't really want to post that here, but after it crashed the last few lines were: [imapx:B] ** Starting next command [imapx:B] - we're selected on 'INBOX', current jobs? [imapx:B] - -120 'FETCH' [imapx:B] - -120 'FETCH' [imapx:B] -- Checking job queue [imapx:B] -- -120 'FETCH'? [imapx:B] --> starting 'FETCH' [imapx:B] completing command buffer is [0] '' [imapx:B] Starting command (active=3,) B01277 UID FETCH 19658 (BODY.PEEK[]<524288.262144>) [imapx:B] I/O: 'B01277 UID FETCH 19658 (BODY.PEEK[]<524288.262144>)' ** GLib-Net:ERROR:gtlsconnection-gnutls.c:688:end_gnutls_io: assertion failed: (!error || !*error) Aborted Cheers.
Thanks for taking the time to report this. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!
Here's the results of a stacktrace. Interestingly this time Evolution seemed to freeze / become non-responsive rather than totally crashing; but maybe that's the result of running it through gdb. ALso, this happened soon after waking my laptop from suspend (evo had been open previous to suspend) - but that's not always been true of this crash. (gdb) thread apply all bt
+ Trace 235008
Thread 1 (Thread 0x7ffff7f8aa40 (LWP 8126))
Thanks for a bug report. evolution-data-server 3.12.9 contains a fix from bug #732018, which wasn't complete, unfortunately, and a new change was added into the development version (see the other bug for more details). Ask your distribution maintainers to backport the other patch too. *** This bug has been marked as a duplicate of bug 732018 ***