Version-Release number of selected component: evolution-3.16.5-3.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: evolution crash_function: _g_log_abort executable: /usr/bin/evolution global_pid: 7136 kernel: 4.1.6-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 frames) #0 _g_log_abort at gmessages.c:315 #10 _gdk_x11_display_send_xevent at gdkmain-x11.c:359 #11 _gdk_x11_display_send_selection_notify at gdkselection-x11.c:329 #12 _gtk_selection_request at gtkselection.c:2554 #13 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #14 _g_closure_invoke_va at gclosure.c:831 #17 gtk_widget_event_internal at gtkwidget.c:7787 #18 gtk_main_do_event at gtkmain.c:1698 #24 gtk_main at gtkmain.c:1219
Created attachment 1077115 [details] File: backtrace
Created attachment 1077116 [details] File: cgroup
Created attachment 1077117 [details] File: core_backtrace
Created attachment 1077118 [details] File: dso_list
Created attachment 1077119 [details] File: environ
Created attachment 1077120 [details] File: limits
Created attachment 1077122 [details] File: maps
Created attachment 1077123 [details] File: mountinfo
Created attachment 1077125 [details] File: namespaces
Created attachment 1077126 [details] File: open_fds
Created attachment 1077128 [details] File: proc_pid_status
Created attachment 1077129 [details] File: var_log_messages
Thanks for a bug report. The backtrace doesn't help much, it shows an error of "The error was 'BadWindow (invalid Window parameter)'", where the var_log_messages also contains a way to debug this issue further. Are you able to reproduce this reliably, after certain steps, please? If yes, what are the steps? Could you try to reproduce using the way the var_log_messages describes it, please?
Unfortunately, as often, I have no idea how to reproduce...