Description of problem: Happened when opening an email Version-Release number of selected component: evolution-3.10.4-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: evolution crash_function: g_mutex_impl_new executable: /usr/bin/evolution kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (10 frames) #2 g_mutex_impl_new at gthread-posix.c:91 #3 g_mutex_init at gthread-posix.c:172 #4 camel_data_wrapper_init at camel-data-wrapper.c:513 #5 g_type_create_instance at gtype.c:1862 #6 g_object_new_internal at gobject.c:1746 #9 camel_mime_message_new at camel-mime-message.c:408 #10 imapx_get_message_sync at camel-imapx-folder.c:563 #11 camel_folder_get_message_sync at camel-folder.c:3838 #12 folder_get_message_thread at camel-folder.c:1251 #13 run_in_thread at gsimpleasyncresult.c:871
Created attachment 893282 [details] File: backtrace
Created attachment 893283 [details] File: cgroup
Created attachment 893284 [details] File: core_backtrace
Created attachment 893285 [details] File: dso_list
Created attachment 893286 [details] File: environ
Created attachment 893287 [details] File: limits
Created attachment 893288 [details] File: maps
Created attachment 893289 [details] File: open_fds
Created attachment 893290 [details] File: proc_pid_status
Created attachment 893291 [details] File: var_log_messages
Thanks for a bug report. The backtrace shows just what you said, a remote message had been read and it was about to be parsed. My guess is that there happened a memory corruption, some kind of use-after-free or similar issue, but I've no better idea here, I'm sorry. Maybe valgrind can show what's going on, but if it's more time-related, then not much luck with the valgrind. By the way, based on the /var/log/messages, is it possible that the message had been downloading when you suddenly lost network connection?
This is first time I've seen this particular crash, so until I know if I at all can reproduce it, I'm not overly keen on running evolution through valgrind. Regarding network connectivity, I'm on a flaky wireless network with a openvpn connection to the imap host so it indeed is very possible that the network did go down.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.