GNOME Bugzilla – Bug 685482
Crash in camel_nntp_raw_commandv()
Last modified: 2015-04-24 11:06:31 UTC
(evolution:6333): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Cannot get message <CvFJZUIX5UbQFAw0@perry.co.uk>: 423 No such article number 69054 (evolution:6333): camel-WARNING **: CamelNNTPFolder::refresh_info_online() reported failure without setting its GError (evolution:6333): camel-WARNING **: CamelNNTPFolder::refresh_info_sync() reported failure without setting its GError (evolution:6333): camel-WARNING **: CamelNNTPStore::get_folder_online() reported failure without setting its GError (evolution:6333): camel-WARNING **: CamelNNTPStore::get_folder_sync() reported failure without setting its GError (evolution:6333): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Cannot get message <ad51etF2v5tU1@mid.individual.net>: 423 No such article number 69056 (evolution:6333): camel-nntp-provider-CRITICAL **: camel_nntp_stream_set_mode: assertion `is != NULL' failed Program received signal SIGSEGV, Segmentation fault.
+ Trace 230961
Thread 140734017914624 (LWP 7895)
Downstream bug report about the same from 3.6.1: https://bugzilla.redhat.com/show_bug.cgi?id=866697
Hmm, I tried to reproduce this, between which I found couple other issues in the code, but I wasn't able to get this particular crash for some reason. Is it reproducible for you too? The downstream reporter said it is, it forced him to disable the NNTP account, thus maybe something in the configuration is causing this?
Yeah, it was fairly reproducible here, and I've disabled NNTP too. Now most of my crashes have gone. Will attempt to re-enable and debug...
I just got the crash, when moving between NNTP folders, I at least thought so, but I cannot reproduce it again - I can freely move between folders now. Pity.
It was crashing here even when I wasn't visiting NNTP folders. That's why I had to disable the account rather than just ignoring it.
For the record, i use news.gmane.org, only as a reader. So maybe that's a non standard implementation, or maybe there is some leftover from my upgrade ( f16 -> f17 -> f18 )
I've experienced random crashes of evolution so it happens during the refresh as well. I've added account in 3.6.x (evolution:16314): camel-nntp-provider-CRITICAL **: camel_nntp_stream_set_mode: assertion `is != NULL' failed
+ Trace 231113
Thread 314 (Thread 0x7fffad1b3700 (LWP 8941))
Inferior 1 [process 16314] will be killed. Quit anyway? (y or n)
Reproduced in openSUSE as well with 3.6.x https://bugzilla.novell.com/show_bug.cgi?id=807614 Trace available in downstream report.
I guess this got obsolete meanwhile, no duplicate since 3.6, while the current stable version is 3.16.1. I also cannot reproduce it. Closing.