Version-Release number of selected component: evolution-data-server-3.12.8-2.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_dbus_connection_signal_unsubscribe executable: /usr/libexec/evolution-calendar-factory kernel: 3.17.4-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 g_dbus_connection_signal_unsubscribe at gdbusconnection.c:3670 #1 on_connection_disconnected at gdbusnamewatching.c:258 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 g_cclosure_marshal_generic at gclosure.c:1448 #9 emit_closed_in_idle at gdbusconnection.c:1386 #13 g_main_context_iteration at gmain.c:3842 #14 dconf_gdbus_worker_thread at dconf-gdbus-thread.c:82 #15 g_thread_proxy at gthread.c:764
Created attachment 978109 [details] File: backtrace
Created attachment 978110 [details] File: cgroup
Created attachment 978111 [details] File: core_backtrace
Created attachment 978112 [details] File: dso_list
Created attachment 978113 [details] File: environ
Created attachment 978114 [details] File: exploitable
Created attachment 978115 [details] File: limits
Created attachment 978116 [details] File: maps
Created attachment 978117 [details] File: open_fds
Created attachment 978118 [details] File: proc_pid_status
Created attachment 978119 [details] File: var_log_messages
Thanks for a bug report. The crashing thread is fully dconf's, evolution's code doesn't use it directly. It can be that this happened due to some incorrect usage of "a common" memory by evolution, but that's something I cannot properly guess from the backtrace. On the other hand evolution-data-server 3.12.8 had an issue which could eventually cause similar crashers. Could you update to the most recent version of evolution packages (3.12.10), please? They contain fixes which should help here. Thanks in advance.
I installed all updates now (including evolution packages (3.12.10)). I don't know anymore what I did to lead to the crash. So I can't verify if this solves the problem.
Thanks for the update. I'm closing this for now, due to lack of a reproducer, but please feel free to reopen or file new bugs, if you get any information with respect of the reproducer and circumstances which would lead to such crash.