Version-Release number of selected component: evolution-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution/evolution-alarm-notify crash_function: g_slice_alloc executable: /usr/libexec/evolution/evolution-alarm-notify global_pid: 2499 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_slice_alloc at gslice.c:539 #3 g_ptr_array_sized_new at garray.c:900 #4 g_ptr_array_new at garray.c:881 #5 g_main_context_new at gmain.c:649 #6 g_dbus_connection_send_message_with_reply_sync at gdbusconnection.c:2134 #7 g_dbus_connection_call_sync_internal at gdbusconnection.c:5930 #8 g_dbus_connection_call_with_unix_fd_list_sync at gdbusconnection.c:6276 #9 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2852 #10 g_dbus_proxy_call_sync at gdbusproxy.c:3044 #11 e_dbus_calendar_call_retrieve_properties_sync at e-dbus-calendar.c:2292
Created attachment 1096803 [details] File: backtrace
Created attachment 1096804 [details] File: cgroup
Created attachment 1096805 [details] File: core_backtrace
Created attachment 1096806 [details] File: dso_list
Created attachment 1096807 [details] File: environ
Created attachment 1096808 [details] File: exploitable
Created attachment 1096809 [details] File: limits
Created attachment 1096810 [details] File: maps
Created attachment 1096811 [details] File: mountinfo
Created attachment 1096812 [details] File: open_fds
Created attachment 1096813 [details] File: proc_pid_status
Thanks for a bug report. I see from the backtrace that the crash happened when one of your calendars had been opened and some final D-Bus calls had been done before fully finishing the open operation. There seems to happen something with the memory, some sort of corruption, according to the upper functions of the backtrace. It's a software memory corruption, like when one part of the code frees memory which other part uses later, or similar programming errors. I do not see anything more from it. By nay chance, do you know what was happening before the crash, please? Especially things like adding new calendars or removing them can be related.
*** This bug has been marked as a duplicate of bug 1281828 ***