Description of problem: Just running Rawhide with normal use, IIRC I had just clicked an email in Evolution. Version-Release number of selected component: gnome-shell-3.12.1-1.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: cogl_object_unref executable: /usr/bin/gnome-shell kernel: 3.15.0-0.rc2.git3.2.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 cogl_object_unref at ./cogl-object.c:112 #1 cogl_handle_unref at ./cogl-object.c:119 #2 st_theme_node_paint_state_node_free_internal at st/st-theme-node-drawing.c:2556 #3 st_theme_node_dispose at st/st-theme-node.c:106 #7 g_hash_table_remove_all_nodes at ghash.c:500 #8 g_hash_table_remove_all at ghash.c:1371 #9 st_theme_context_changed at st/st-theme-context.c:230 #13 g_signal_emit_by_name at gsignal.c:3403 #14 object_set_property at gobject.c:1378 #15 g_object_set_property at gobject.c:2306
Created attachment 890882 [details] File: backtrace
Created attachment 890883 [details] File: cgroup
Created attachment 890884 [details] File: core_backtrace
Created attachment 890885 [details] File: dso_list
Created attachment 890886 [details] File: environ
Created attachment 890887 [details] File: limits
Created attachment 890888 [details] File: maps
Created attachment 890889 [details] File: open_fds
Created attachment 890890 [details] File: proc_pid_status
Created attachment 890891 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
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.