Version-Release number of selected component: evolution-data-server-3.10.4-3.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_child_source_remove_internal executable: /usr/libexec/evolution-calendar-factory kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 500 Truncated backtrace: Thread no. 1 (4 frames) #0 g_child_source_remove_internal at gmain.c:1448 #1 g_source_destroy_internal at gmain.c:1227 #6 gdbus_shared_thread_func at gdbusprivate.c:278 #7 g_thread_proxy at gthread.c:798
Created attachment 908937 [details] File: backtrace
Created attachment 908938 [details] File: cgroup
Created attachment 908939 [details] File: core_backtrace
Created attachment 908940 [details] File: dso_list
Created attachment 908941 [details] File: environ
Created attachment 908942 [details] File: exploitable
Created attachment 908943 [details] File: limits
Created attachment 908944 [details] File: maps
Created attachment 908945 [details] File: open_fds
Created attachment 908946 [details] File: proc_pid_status
Created attachment 908947 [details] File: var_log_messages
Thanks for a bug report. I guess this crashed due to some memory corruption, like when some part of the code writes to an already freed memory. I guess so due to the place of the crash. I guess this just happened in the background, probably after some periodic update of one of your configured calendars, even it is not visible from the backtrace at all.