Version-Release number of selected component: evolution-data-server-3.17.90-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/evolution-calendar-factory crash_function: g_dbus_proxy_call_sync_internal executable: /usr/libexec/evolution-calendar-factory global_pid: 22002 kernel: 4.2.0-0.rc8.git0.1.fc23.x86_64+debug runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 g_dbus_proxy_call_sync_internal at gdbusproxy.c:2834 #1 g_dbus_proxy_call_sync at gdbusproxy.c:3044 #2 e_dbus_subprocess_backend_call_create_sync at e-dbus-subprocess-backend.c:561 #3 data_factory_call_subprocess_backend_create_sync at e-data-factory.c:530 #4 data_factory_spawn_subprocess_backend at e-data-factory.c:1230 #5 data_factory_spawn_subprocess_backend_in_thread at e-data-factory.c:1337 #6 g_thread_proxy at gthread.c:778
Created attachment 1069159 [details] File: backtrace
Created attachment 1069160 [details] File: cgroup
Created attachment 1069161 [details] File: core_backtrace
Created attachment 1069162 [details] File: dso_list
Created attachment 1069163 [details] File: environ
Created attachment 1069164 [details] File: exploitable
Created attachment 1069165 [details] File: limits
Created attachment 1069166 [details] File: maps
Created attachment 1069167 [details] File: mountinfo
Created attachment 1069168 [details] File: namespaces
Created attachment 1069169 [details] File: open_fds
Created attachment 1069170 [details] File: proc_pid_status
Thanks for a bug report. I see from the backtrace that the factory crashed due to trying to open an On This Computer/Personal task list, while the factory was closing itself. Kind of corner case, from my point of view, but still doable. I fixed this upstream [1] for evolution-data-server 3.17.92+. [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=e9dba19