After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685482 - Crash in camel_nntp_raw_commandv()
Crash in camel_nntp_raw_commandv()
Status: RESOLVED OBSOLETE
Product: evolution-data-server
Classification: Platform
Component: Mailer
3.6.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-10-04 09:07 UTC by David Woodhouse
Modified: 2015-04-24 11:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Woodhouse 2012-10-04 09:07:12 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.

Thread 140734017914624 (LWP 7895)

  • #0 camel_nntp_raw_commandv
    at camel-nntp-store.c line 1544
  • #1 camel_nntp_raw_command_auth
    at camel-nntp-store.c line 1674
  • #2 camel_nntp_command
    at camel-nntp-store.c line 1738
  • #3 nntp_folder_refresh_info_online
    at camel-nntp-folder.c line 194
  • #4 disco_refresh_info_sync
    at camel-disco-folder.c line 314
  • #5 disco_refresh_info_sync
    at camel-disco-folder.c line 298
  • #6 camel_folder_refresh_info_sync
    at camel-folder.c line 3991
  • #7 camel_nntp_folder_new
    at camel-nntp-folder.c line 816
  • #8 disco_store_get_folder_sync
  • #9 camel_store_get_folder_sync
  • #10 e_mail_session_uri_to_folder_sync
  • #11 refresh_folders_exec
    at mail-send-recv.c line 1043
  • #12 mail_msg_proxy
    at mail-mt.c line 423
  • #13 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #14 g_thread_proxy
    at gthread.c line 797
  • #15 start_thread
    at pthread_create.c line 308
  • #16 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 114

Comment 1 Milan Crha 2012-10-18 09:40:13 UTC
Downstream bug report about the same from 3.6.1:
https://bugzilla.redhat.com/show_bug.cgi?id=866697
Comment 2 Milan Crha 2012-10-18 12:36:38 UTC
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?
Comment 3 David Woodhouse 2012-10-18 14:47:04 UTC
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...
Comment 4 Milan Crha 2012-10-18 16:13:19 UTC
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.
Comment 5 David Woodhouse 2012-10-18 17:38:54 UTC
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.
Comment 6 misc 2012-10-18 20:35:38 UTC
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 )
Comment 7 Maciej (Matthew) Piechotka 2012-10-30 20:20:59 UTC
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

Thread 314 (Thread 0x7fffad1b3700 (LWP 8941))

  • #0 camel_nntp_raw_commandv
    at camel-nntp-store.c line 1544
  • #1 camel_nntp_raw_command_auth
    at camel-nntp-store.c line 1674
  • #2 camel_nntp_command
    at camel-nntp-store.c line 1738
  • #3 nntp_folder_refresh_info_online
    at camel-nntp-folder.c line 194
  • #4 disco_refresh_info_sync
    at camel-disco-folder.c line 314
  • #5 disco_refresh_info_sync
    at camel-disco-folder.c line 298
  • #6 camel_folder_refresh_info_sync
    at camel-folder.c line 3991
  • #7 camel_nntp_folder_new
    at camel-nntp-folder.c line 816
  • #8 disco_store_get_folder_sync
  • #9 camel_store_get_folder_sync
  • #10 e_mail_session_uri_to_folder_sync
  • #11 refresh_folders_exec
    at mail-send-recv.c line 1043
  • #12 mail_msg_proxy
    at mail-mt.c line 423
  • #13 g_thread_pool_thread_proxy
    at gthreadpool.c line 309
  • #14 g_thread_proxy
    at gthread.c line 797
  • #15 start_thread
    at pthread_create.c line 305
  • #16 clone
    at ../sysdeps/unix/sysv/linux/x86_64/clone.S line 115

	Inferior 1 [process 16314] will be killed.

Quit anyway? (y or n)
Comment 8 Bjørn Lie 2013-03-05 21:21:51 UTC
Reproduced in openSUSE as well with 3.6.x

https://bugzilla.novell.com/show_bug.cgi?id=807614

Trace available in downstream report.
Comment 9 Milan Crha 2015-04-24 11:06:31 UTC
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.