Version-Release number of selected component: evolution-data-server-3.16.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: strlen executable: /usr/libexec/evolution-addressbook-factory global_pid: 2400 kernel: 4.0.0-0.rc5.git4.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at Tue 2015-03-10 00:36:57 EET, end at Fri 2015-04-24 09:19:42 EEST. -- Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 g_strdup at gstrfuncs.c:355 #2 schedule_call_in_idle at gdbusnamewatching.c:192 #3 do_call at gdbusnamewatching.c:214 #4 ffi_call_unix64 at ../src/x86/unix64.S:76 #5 ffi_call at ../src/x86/ffi64.c:525 #6 g_cclosure_marshal_generic at gclosure.c:1448 #11 emit_closed_in_idle at gdbusconnection.c:1386 #16 source_registry_object_manager_thread at e-source-registry.c:1160 #17 g_thread_proxy at gthread.c:764
Created attachment 1024171 [details] File: backtrace
Created attachment 1024172 [details] File: cgroup
Created attachment 1024173 [details] File: core_backtrace
Created attachment 1024174 [details] File: dso_list
Created attachment 1024175 [details] File: environ
Created attachment 1024176 [details] File: limits
Created attachment 1024177 [details] File: maps
Created attachment 1024178 [details] File: mountinfo
Created attachment 1024179 [details] File: namespaces
Created attachment 1024180 [details] File: open_fds
Created attachment 1024181 [details] File: proc_pid_status
Thanks for a bug report. This crashed in a GDBus code, thus part of glib2. By any chance, do you have any steps or a reproducer for the crash, please?
No, I have google calendar added and when opening some notifications this crash happens but not always. Not sure what is the connection nor how to reproduce. Feel free to close it if the backtrace is not valuable hint.
Okay. The backtrace is pretty clean, the crash happened in a thread, in a GDBus code, which could, or not, be due to some oddities in the evolution-data-server code. Let's reopen if there'll be more cases.