Description of problem: Crash occurred right after cold boot and loigin. Version-Release number of selected component: evolution-data-server-3.24.5-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-source-registry crash_function: g_hash_table_lookup_node executable: /usr/libexec/evolution-source-registry journald_cursor: s=63d9f8c329544f1cbda8a56f502dd65b;i=1a829;b=55e278f7170a4a73a56f2118d6df4515;m=546d75f;t=558a45f148c5f;x=6ed045e8190ddc29 kernel: 4.12.9-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Potential duplicate: bug 1272252
Created attachment 1323552 [details] File: backtrace
Created attachment 1323553 [details] File: cgroup
Created attachment 1323554 [details] File: core_backtrace
Created attachment 1323555 [details] File: cpuinfo
Created attachment 1323556 [details] File: dso_list
Created attachment 1323557 [details] File: environ
Created attachment 1323558 [details] File: limits
Created attachment 1323559 [details] File: maps
Created attachment 1323560 [details] File: open_fds
Created attachment 1323561 [details] File: proc_pid_status
Created attachment 1323562 [details] File: var_log_messages
Thanks for a bug report. The backtrace shows some crash related to GNOME Online Accounts account, when goa-daemon reported some property change on it. There is not much related to evolution-data-server in the backtrace, it's all about GDBus and GOA. The same thing had been reported in bug #1486763, which I moved to glib2. It's not necessarily glib2 issue, it can be that the GOA object doesn't unregister signal listener or anything like that. *** This bug has been marked as a duplicate of bug 1486763 ***