Version-Release number of selected component: gnome-settings-daemon-3.16.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/gnome-settings-daemon crash_function: _g_log_abort executable: /usr/libexec/gnome-settings-daemon global_pid: 2417 kernel: 4.1.6-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #10 finish_selection_request at gsd-clipboard-manager.c:179 #11 convert_clipboard at gsd-clipboard-manager.c:661 #12 clipboard_manager_process_event at gsd-clipboard-manager.c:807 #13 clipboard_manager_event_filter at gsd-clipboard-manager.c:823 #14 gdk_event_apply_filters at gdkeventsource.c:81 #15 gdk_event_source_translate_event at gdkeventsource.c:202 #16 _gdk_x11_display_queue_events at gdkeventsource.c:338 #17 gdk_display_get_event at gdkdisplay.c:340 #23 gtk_main at gtkmain.c:1219
Created attachment 1073189 [details] File: backtrace
Created attachment 1073190 [details] File: cgroup
Created attachment 1073191 [details] File: core_backtrace
Created attachment 1073192 [details] File: dso_list
Created attachment 1073193 [details] File: environ
Created attachment 1073194 [details] File: limits
Created attachment 1073195 [details] File: maps
Created attachment 1073196 [details] File: mountinfo
Created attachment 1073197 [details] File: namespaces
Created attachment 1073198 [details] File: open_fds
Created attachment 1073199 [details] File: proc_pid_status
Created attachment 1073200 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.