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 598932 - evolution crashed with SIGSEGV in camel_msgport_try_pop()
evolution crashed with SIGSEGV in camel_msgport_try_pop()
Status: RESOLVED DUPLICATE of bug 581847
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
: 608973 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-10-19 14:23 UTC by Pedro Villavicencio
Modified: 2011-01-10 16:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Pedro Villavicencio 2009-10-19 14:23:21 UTC
this report has been filed here:

"i was trying to configure an email account and evolution crash"

".

Thread 1 (process 2276)

  • #0 camel_msgport_try_pop
    at camel-msgport.c line 402
  • #1 camel_operation_cancel_check
    at camel-operation.c line 405
  • #2 stream_write
    at camel-tcp-stream-ssl.c line 422
  • #3 camel_stream_write
    at camel-stream.c line 116
  • #4 camel_stream_printf
    at camel-stream.c line 228
  • #5 imap_command_start
    at camel-imap-command.c line 223
  • #6 camel_imap_command
    at camel-imap-command.c line 109
  • #7 imap_command_start
    at camel-imap-command.c line 195
  • #8 camel_imap_command
    at camel-imap-command.c line 109
  • #9 camel_imap_folder_fetch_data
    at camel-imap-folder.c line 3820
  • #10 write_to_stream
    at camel-imap-wrapper.c line 139
  • #11 camel_data_wrapper_write_to_stream
    at camel-data-wrapper.c line 171
  • #12 decode_to_stream
    at camel-data-wrapper.c line 210
  • #13 camel_data_wrapper_decode_to_stream
    at camel-data-wrapper.c line 233
  • #14 camel_mime_part_get_content_size
    at camel-mime-part.c line 1108
  • #15 e_attachment_load_async
    from /usr/lib/evolution/2.28/libemiscwidgets.so.0
  • #16 ??
    from /usr/lib/evolution/2.28/components/libevolution-mail.so
  • #17 ??
    from /usr/lib/evolution/2.28/components/libevolution-mail.so
  • #18 html_g_cclosure_marshal_BOOLEAN__OBJECT
    at htmlmarshal.c line 81
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 html_engine_object_requested_cb
    at gtkhtml.c line 550
  • #24 html_g_cclosure_marshal_BOOLEAN__OBJECT
    at htmlmarshal.c line 81
  • #25 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #26 ??
    from /usr/lib/libgobject-2.0.so.0
  • #27 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #28 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #29 element_parse_object
    at htmlengine.c line 1624
  • #30 parse_one_token
    at htmlengine.c line 3975
  • #31 html_engine_timer_event
    at htmlengine.c line 1429
  • #32 html_engine_flush
    at htmlengine.c line 6897
  • #33 gtk_html_flush
    at gtkhtml.c line 6327
  • #34 ??
    from /usr/lib/evolution/2.28/components/libevolution-mail.so
  • #35 ??
    from /usr/lib/evolution/2.28/libevolution-mail-shared.so.0
  • #36 ??
    from /lib/libglib-2.0.so.0
  • #37 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #38 ??
    from /lib/libglib-2.0.so.0
  • #39 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #40 bonobo_main
    at bonobo-main.c line 311
  • #41 ??
  • #42 __libc_start_main
    at libc-start.c line 220
  • #43 ??

Comment 1 Akhil Laddha 2009-11-12 03:42:18 UTC
looks dupe of bug 598932
Comment 2 Akhil Laddha 2009-11-12 03:43:13 UTC
(In reply to comment #1)
> looks dupe of bug 598932

oh .. this comment was for bug 600882
Comment 3 Akhil Laddha 2010-09-30 03:34:08 UTC
*** Bug 608973 has been marked as a duplicate of this bug. ***
Comment 4 Milan Crha 2011-01-10 16:41:23 UTC

*** This bug has been marked as a duplicate of bug 581847 ***