Version-Release number of selected component: evolution-data-server-3.10.3-1.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_source_callback_ref executable: /usr/libexec/evolution-calendar-factory kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 g_source_callback_ref at gmain.c:1537 #5 dbus_server_run_server at e-dbus-server.c:222 #6 ffi_call_unix64 at ../src/x86/unix64.S:76 #7 ffi_call at ../src/x86/ffi64.c:522 #8 g_cclosure_marshal_generic_va at gclosure.c:1550 #9 _g_closure_invoke_va at gclosure.c:840 #12 e_dbus_server_run at e-dbus-server.c:411
Created attachment 848192 [details] File: backtrace
Created attachment 848193 [details] File: cgroup
Created attachment 848194 [details] File: core_backtrace
Created attachment 848195 [details] File: dso_list
Created attachment 848196 [details] File: environ
Created attachment 848197 [details] File: exploitable
Created attachment 848198 [details] File: limits
Created attachment 848199 [details] File: maps
Created attachment 848200 [details] File: open_fds
Created attachment 848201 [details] File: proc_pid_status
Created attachment 848202 [details] File: var_log_messages
Thanks for a bug report. I see this happened probably due to some memory corruption, caused by a software writing to already freed memory or some similar kind of issue, but I cannot tell from the backtrace why that happened. Maybe this is related to bug #872652, but I cannot tell for sure. Do you recall what was happening before the crash, please? I do not mean several seconds, but in general, like after you logged in the machine till the ABRT report showed up. For example, did it crash right after login, or a long time after it?
Hi Milan, It was in January adn i don't remember. Now, i use thunderbird instead of evolution. Sorry Ciao Martin