Version-Release number of selected component: evolution-data-server-3.10.4-1.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/libexec/evolution-source-registry crash_function: g_thread_new executable: /usr/libexec/evolution-source-registry kernel: 3.13.3-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (8 frames) #2 g_thread_new at gthread.c:840 #3 e_ews_connection_utils_unref_in_thread at /usr/lib64/evolution-data-server/libeews-1.2.so.0 #4 ews_response_cb at /usr/lib64/evolution-data-server/libeews-1.2.so.0 #5 soup_session_process_queue_item at soup-session.c:1873 #6 async_run_queue at soup-session.c:1911 #7 idle_run_queue at soup-session.c:1945 #12 e_ews_soup_thread at /usr/lib64/evolution-data-server/libeews-1.2.so.0 #13 g_thread_proxy at gthread.c:798
Created attachment 866230 [details] File: backtrace
Created attachment 866231 [details] File: cgroup
Created attachment 866232 [details] File: core_backtrace
Created attachment 866233 [details] File: dso_list
Created attachment 866234 [details] File: environ
Created attachment 866235 [details] File: limits
Created attachment 866236 [details] File: maps
Created attachment 866237 [details] File: open_fds
Created attachment 866238 [details] File: proc_pid_status
Created attachment 866239 [details] File: var_log_messages
Thanks for a bug report. This is quite the same case as in bug #1068741, from which I guess my note about the calendars is wrong. Could this happen due to an update of your machine, causing crash of multiple evolution-related processes? I'm marking this as a duplicate of the other bug report, to deal with this within one bug only. *** This bug has been marked as a duplicate of bug 1068741 ***
I got another of these this morning according to abrt.