Bug 635675 – [abrt] evolution-2.32.1-1.fc14: g_object_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

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 635675 - [abrt] evolution-2.32.1-1.fc14: g_object_unref: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)


Summary:	[abrt] evolution-2.32.1-1.fc14: g_object_unref: Process /usr/bin/evolution wa...


Status:	RESOLVED OBSOLETE

Product:	evolution
Classification:	Applications
Component:	Mailer
Version:	2.32.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:	2010-11-24 10:03 UTC by Milan Crha
Modified:	2012-09-04 18:58 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
stack trace (44.95 KB, text/plain) 2011-09-20 16:43 UTC, Christian Kirbach	Details

Description Milan Crha 2010-11-24 10:03:53 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=656442

abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_object_unref
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290529733
uid: 501

How to reproduce
-----
1. I only delete my message

Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 224807

Thread 18 (Thread 1616)

#0 fdatasync
from /lib64/libc.so.6
#1 full_fsync
at sqlite3.c line 25213
#2 unixSync
at sqlite3.c line 25261
#3 sync_request_thread_cb
at camel-db.c line 104
#4 g_thread_create_proxy
at gthread.c line 1897
#5 start_thread
from /lib64/libpthread.so.0
#6 clone
from /lib64/libc.so.6

Thread 17 (Thread 1617)

#0 open64
from /lib64/libc.so.6
#1 _IO_new_file_fopen
from /lib64/libc.so.6
#2 __fopen_internal
from /lib64/libc.so.6
#3 camel_object_state_write
at camel-object.c line 450
#4 local_sync
at camel-local-folder.c line 521
#5 camel_folder_sync
at camel-folder.c line 1124
#6 mail_msg_proxy
at mail-mt.c line 469
#7 g_thread_pool_thread_proxy
at gthreadpool.c line 319
#8 g_thread_create_proxy
at gthread.c line 1897
#9 start_thread
from /lib64/libpthread.so.0
#10 clone
from /lib64/libc.so.6

Thread 15 (Thread 1615)

#0 pthread_join
from /lib64/libpthread.so.0
#1 g_thread_join_posix_impl
at gthread-posix.c line 385
#2 g_thread_join
at gthread.c line 2042
#3 camel_sqlite3_file_xClose
at camel-db.c line 212
#4 sqlite3OsClose
at sqlite3.c line 12541
#5 pager_end_transaction
at sqlite3.c line 33500
#6 sqlite3PagerCommitPhaseTwo
at sqlite3.c line 36955
#7 sqlite3BtreeCommitPhaseTwo
at sqlite3.c line 41628
#8 vdbeCommit
at sqlite3.c line 49940
#9 sqlite3VdbeHalt
at sqlite3.c line 50342
#10 sqlite3VdbeExec
at sqlite3.c line 56007
#11 sqlite3Step
at sqlite3.c line 51732
#12 sqlite3_step
at sqlite3.c line 51792
#13 sqlite3_exec
at sqlite3.c line 76845
#14 cdb_sql_exec
at camel-db.c line 377
#15 camel_db_end_transaction
at camel-db.c line 616
#16 folder_changed_change
at camel-vee-folder.c line 538
#17 session_thread_proxy
at camel-session.c line 321
#18 g_thread_pool_thread_proxy
at gthreadpool.c line 319
#19 g_thread_create_proxy
at gthread.c line 1897
#20 start_thread
from /lib64/libpthread.so.0
#21 clone
from /lib64/libc.so.6

Thread 1 (Thread 1524)

#0 g_object_unref
at gobject.c line 2629
#1 data_wrapper_dispose
at camel-data-wrapper.c line 60
#2 g_object_unref
at gobject.c line 2658
#3 medium_dispose
at camel-medium.c line 96
#4 g_object_unref
at gobject.c line 2658
#5 g_list_foreach
at glist.c line 919
#6 multipart_dispose
at camel-multipart.c line 47
#7 g_object_unref
at gobject.c line 2658
#8 medium_dispose
at camel-medium.c line 96
#9 g_object_unref
at gobject.c line 2658
#10 g_list_foreach
at glist.c line 919
#11 multipart_dispose
at camel-multipart.c line 47
#12 g_object_unref
at gobject.c line 2658
#13 medium_dispose
at camel-medium.c line 96
#14 g_object_unref
at gobject.c line 2658
#15 emf_format_clone
at em-format.c line 240
#16 efh_format_timeout
at em-format-html.c line 327
#17 mail_reader_message_loaded_cb
at e-mail-reader.c line 2233
#18 mail_msg_idle_cb
at mail-mt.c line 451
#19 g_main_dispatch
at gmain.c line 2149
#20 g_main_context_dispatch
at gmain.c line 2702
#21 g_main_context_iterate
at gmain.c line 2780
#22 g_main_loop_run
at gmain.c line 2988
#23 IA__gtk_main
at gtkmain.c line 1237
#24 main
at main.c line 679

Comment 1 Jesse Brandeburg 2011-01-18 06:53:38 UTC

I've also seen this bug, and be sure to check the linked post for many other users reporting the same.

Will there be someone looking into this bug?

Comment 2 Milan Crha 2011-01-18 08:23:31 UTC

This seems to be related to message structure too, and the reproducer steps are sort of vague, thus if you can find a test message and exact steps to a reproducer, then it'll surely help with a fix for this bug.

Comment 3 Jesse Brandeburg 2011-01-18 17:12:59 UTC

I'm connected to an exchange 2007 server via IMAP, and am doing typical things when this issue occurs.

The last thing I did when I saw this issue was delete a couple of messages in quick succession and then ctrl-e expunge the folder.

I'll watch for the issue to reoccur and try to report any other details.

Comment 4 Christian Kirbach 2011-09-20 16:42:22 UTC

I just hit this, too

attaching my trace

Comment 5 Christian Kirbach 2011-09-20 16:43:07 UTC

Created attachment 197087 [details]
stack trace

Comment 6 Milan Crha 2012-09-04 18:58:51 UTC

Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.