Description of problem: Just suddenly crashed on me right after I'd opened a new tab in Chrome. Version-Release number of selected component: cinnamon-settings-daemon-2.6.3-4.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/libexec/cinnamon-settings-daemon crash_function: _g_log_abort executable: /usr/libexec/cinnamon-settings-daemon global_pid: 2275 kernel: 4.1.4-200.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 send_selection_notify at csd-clipboard-manager.c:153 #11 clipboard_manager_process_event at csd-clipboard-manager.c:786 #12 clipboard_manager_event_filter at csd-clipboard-manager.c:824 #13 gdk_event_apply_filters at gdkeventsource.c:81 #14 gdk_event_source_translate_event at gdkeventsource.c:202 #15 _gdk_x11_display_queue_events at gdkeventsource.c:338 #16 gdk_display_get_event at gdkdisplay.c:340 #22 gtk_main at gtkmain.c:1219
Created attachment 1073351 [details] File: backtrace
Created attachment 1073352 [details] File: cgroup
Created attachment 1073353 [details] File: core_backtrace
Created attachment 1073354 [details] File: dso_list
Created attachment 1073355 [details] File: environ
Created attachment 1073356 [details] File: limits
Created attachment 1073357 [details] File: maps
Created attachment 1073358 [details] File: mountinfo
Created attachment 1073359 [details] File: namespaces
Created attachment 1073360 [details] File: open_fds
Created attachment 1073361 [details] File: proc_pid_status
Created attachment 1073362 [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.