Version-Release number of selected component: evolution-data-server-3.18.2-2.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/libexec/evolution-source-registry crash_function: g_str_hash executable: /usr/libexec/evolution-source-registry global_pid: 3637 kernel: 4.2.6-301.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_str_hash at ghash.c:1875 #1 g_hash_table_lookup_node at ghash.c:375 #2 g_hash_table_lookup at ghash.c:1147 #3 _g_dbus_object_proxy_add_interface at gdbusobjectproxy.c:301 #4 add_interfaces at gdbusobjectmanagerclient.c:1536 #5 process_get_all_result at gdbusobjectmanagerclient.c:1647 #6 initable_init at gdbusobjectmanagerclient.c:1400 #7 g_initable_new_valist at ginitable.c:228 #8 g_initable_new at ginitable.c:146 #9 goa_object_manager_client_new_for_bus_sync at goa-generated.c:24951 Potential duplicate: bug 810649
Created attachment 1106371 [details] File: backtrace
Created attachment 1106372 [details] File: cgroup
Created attachment 1106373 [details] File: core_backtrace
Created attachment 1106374 [details] File: dso_list
Created attachment 1106375 [details] File: environ
Created attachment 1106376 [details] File: exploitable
Created attachment 1106377 [details] File: limits
Created attachment 1106378 [details] File: maps
Created attachment 1106379 [details] File: mountinfo
Created attachment 1106380 [details] File: namespaces
Created attachment 1106381 [details] File: open_fds
Created attachment 1106382 [details] File: proc_pid_status
Thanks for a bug report. The crash looks new to me, the most confusing thing is that it crashed while creating a new GObject descendant. By any chance, do you have any steps how to reproduce the crash, please?
Unfortunately not, and it hasn't happened recently. Somewhere Fedora has also updated evolution to 3.18.3-1, so you can probably delete this.
Thanks for the update. I'm afraid this is some kind of coincidence, which leads to the crash. I do not know what coincidence, though. Let's close this for now, but feel free to reopen or file new bugs, if it crashes again.
*** Bug 1304087 has been marked as a duplicate of this bug. ***
I just got another occurrence of this under the duplicated bug #1304087, but also/still with no known way to reproduce. ABRT caught it.