GNOME Bugzilla – Bug 648726
[abrt] evolution-3.0.0-1.fc15: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2013-08-22 16:48:11 UTC
Moving this from a downstream bug report: https://bugzilla.redhat.com/show_bug.cgi?id=699656 abrt version: 2.0.1 uid: 500 cmdline: /usr/bin/evolution component: evolution crash_function: imapx_expunge_uid_from_summary kernel: 2.6.38.3-18.fc15.x86_64 reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV) executable: /usr/bin/evolution architecture: x86_64 username: odeda package: evolution-3.0.0-1.fc15 rating: 4 time: 1303777431 os_release: Fedora release 15 (Lovelock) Core was generated by `/usr/bin/evolution'. Program terminated with signal 11, Segmentation fault.
+ Trace 226891
Thread 1 (Thread 0x7f15e5779700 (LWP 6893))
I got a similar crash in master (3.1.4) while evolution was idle. Program received signal SIGSEGV, Segmentation fault.
+ Trace 227877
Thread 3 (Thread 0xb56ffb70 (LWP 17872))
$1 = (GArray *) 0x0 (gdb) p finfo->got $2 = 1060 (gdb) p *job $3 = {msg = {ln = {next = 0x95d7598, prev = 0x86ab6c0}, reply_port = 0x89e4198, flags = 0}, cancellable = 0xae33b688, error = 0x0, start = 0xb2fa9a8f <imapx_job_fetch_new_messages_start>, noreply = 0, type = 8, pri = 0, commands = 0, folder = 0x88e86d8, u = {get_message = {uid = 0x0, stream = 0x0, body_offset = 0, body_len = 0, fetch_offset = 0, size = 0, use_multi_fetch = 0}, refresh_info = {infos = 0x0, index = 0, last_index = 0, update_unseen = 0, uidset = { ie = 0x0, entries = 0, uids = 0, total = 0, limit = 0, start = 0, last = 0}, changes = 0xad6b8848}, sync_changes = {changed_uids = 0x0, on_set = 0, off_set = 0, on_user = 0x0, off_user = 0x0, unread_change = 0}, append_message = {path = 0x0, info = 0x0}, copy_messages = {dest = 0x0, uids = 0x0, delete_originals = 0, index = 0, last_index = 0, uidset = {ie = 0x0, entries = 0, uids = 0, total = 0, limit = 0, start = 0, last = 2909505608}}, list = {pattern = 0x0, flags = 0, ext = 0x0, folders = 0x0}, manage_subscriptions = {folder_name = 0x0, subscribe = 0}, rename_folder = {ofolder_name = 0x0, nfolder_name = 0x0}, folder_name = 0x0}} (gdb) p (finfo->got & 32) $4 = 32 (gdb) p (finfo->got & 64) $5 = 0 (gdb) p (finfo->got & 32) $6 = 32 (gdb) p finfo->flags $7 = 0 (gdb) p finfo->user_flags $8 = (struct _CamelFlag *) 0x0
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.
reproduced in evolution 3.4.4-3.fc17.x86_64, but the bug upload tool detected a duplicate and did not upload anything.
I can also confirm that this is still relevant. Just had a crash today with evolution-3.4.4-2.fc17.x86_64.
Closing as OBSOLETE because the stack trace is too old to be useful.