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: __pthread_mutex_lock executable: /usr/bin/evolution kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66 #1 g_mutex_lock at gthread-posix.c:213 #2 g_main_loop_quit at gmain.c:3932 #3 source_registry_authenticate_respond_cb at e-source-registry.c:1777 #7 g_main_context_iteration at gmain.c:3774 #8 e_source_registry_authenticate_sync at e-source-registry.c:2119 #9 mail_session_authenticate_sync at e-mail-session.c:1608 #10 camel_session_authenticate_sync at camel-session.c:1829 #11 ews_connect_sync at camel-ews-store.c:658 #12 service_connect_thread at camel-service.c:773
Created attachment 896490 [details] File: backtrace
Created attachment 896491 [details] File: cgroup
Created attachment 896492 [details] File: core_backtrace
Created attachment 896493 [details] File: dso_list
Created attachment 896494 [details] File: environ
Created attachment 896495 [details] File: exploitable
Created attachment 896496 [details] File: limits
Created attachment 896497 [details] File: maps
Created attachment 896498 [details] File: open_fds
Created attachment 896499 [details] File: proc_pid_status
Created attachment 896500 [details] File: var_log_messages
Thanks for a bug report. I would guess from the backtrace that there happened some memory corruption, like when some part of the code accesses an already freed memory, but I do not see in the backtrace how that could happen. The problem is that such memory corruptions can happen in one time and strike later. Do you have any steps of clues how to reproduce this, please? Basically anything what could help to identify the cause.
I can't help. This crashes is without user assistance.
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.