Bug 519537 – evolution crashed with SIGSEGV in camel_folder_get_message()

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 519537 - evolution crashed with SIGSEGV in camel_folder_get_message()


Summary:	evolution crashed with SIGSEGV in camel_folder_get_message()


Status:	RESOLVED DUPLICATE of bug 522389

Product:	evolution-data-server
Classification:	Platform
Component:	Mailer
Version:	2.22.x (obsolete)
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mail-maintainers
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-02-29 15:18 UTC by Pedro Villavicencio
Modified:	2008-09-17 17:29 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description Pedro Villavicencio 2008-02-29 15:18:04 UTC

This report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/evolution/+bug/197004

"Crashed when viewing a message which it has done fairly frequently recently. Doesn't seem to be anything in common our out of the ordinary with the emails. Using with a Novell Groupwise system."

".

+ Trace 190857

Thread 4 (process 16202)

#0 fsync
from /lib/libpthread.so.0
#1 e_xml_save_file
at e-xml-utils.c line 103
#2 emft_save_state
at em-folder-tree.c line 2584
#3 g_timeout_dispatch
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 3499
#4 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2065
#5 g_main_context_iterate
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2698
#6 IA__g_main_loop_run
at /build/buildd/glib2.0-2.15.6/glib/gmain.c line 2906
#7 bonobo_main
at bonobo-main.c line 311
#8 main
at main.c line 721
#9 __libc_start_main
from /lib/libc.so.6
#10 _start

Thread 2 (process 16221)

#0 fsync
from /lib/libpthread.so.0
#1 camel_store_summary_save
at camel-store-summary.c line 475
#2 groupwise_refresh_info
at camel-groupwise-folder.c line 1002
#3 mail_msg_proxy
at mail-mt.c line 523
#4 g_thread_pool_thread_proxy
at /build/buildd/glib2.0-2.15.6/glib/gthreadpool.c line 265
#5 g_thread_create_proxy
at /build/buildd/glib2.0-2.15.6/glib/gthread.c line 635
#6 start_thread
from /lib/libpthread.so.0
#7 clone
from /lib/libc.so.6
#8 ??

Thread 1 (process 16224)

#0 groupwise_folder_item_to_msg
at camel-groupwise-folder.c line 1694
#1 groupwise_folder_get_message
at camel-groupwise-folder.c line 178
#2 camel_folder_get_message
at camel-folder.c line 1073
#3 get_message_exec
at mail-ops.c line 1720
#4 mail_msg_proxy
at mail-mt.c line 523
#5 g_thread_pool_thread_proxy
at /build/buildd/glib2.0-2.15.6/glib/gthreadpool.c line 265
#6 g_thread_create_proxy
at /build/buildd/glib2.0-2.15.6/glib/gthread.c line 635
#7 start_thread
from /lib/libpthread.so.0
#8 clone
from /lib/libc.so.6
#9 ??

Comment 1 Matthew Barnes 2008-03-11 00:34:29 UTC

Bumping version to a stable release.

Comment 2 Kieran Hogg 2008-03-13 11:01:43 UTC

I can't reproduce this with the same version and messages on a non-64bit machine so it looks like it's restricted to that.

Comment 3 Tobias Mueller 2008-03-17 14:50:43 UTC

Looks like bug 522389 or bug 522368 which crashes on a certain email.

Comment 4 Milan Crha 2008-09-17 17:29:27 UTC

I believe you've right, Tobias. Thus marking as duplicate of the one with proper patch.

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