Description of problem: running in terminal yum update Version-Release number of selected component: gnome-shell-3.13.1-2.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: get_radeon_bo executable: /usr/bin/gnome-shell kernel: 3.15.0-0.rc5.git4.1.fc21.x86_64 runlevel: 5 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 get_radeon_bo at radeon_drm_bo.c:91 #1 radeon_cs_create_fence at radeon_drm_cs.c:611 #2 radeon_drm_cs_flush at radeon_drm_cs.c:472 #3 r600_context_gfx_flush at r600_hw_context.c:277 #4 st_context_flush at state_tracker/st_manager.c:500 #5 dri_flush at dri_drawable.c:519 #6 __dri2CopySubBuffer at dri2_glx.c:595 #7 _cogl_winsys_onscreen_swap_region at winsys/cogl-winsys-glx.c:1831 #8 cogl_onscreen_swap_region at ./cogl-onscreen.c:370 #9 clutter_stage_cogl_redraw at cogl/clutter-stage-cogl.c:644
Created attachment 899655 [details] File: backtrace
Created attachment 899656 [details] File: cgroup
Created attachment 899657 [details] File: core_backtrace
Created attachment 899658 [details] File: dso_list
Created attachment 899659 [details] File: environ
Created attachment 899660 [details] File: exploitable
Created attachment 899661 [details] File: limits
Created attachment 899662 [details] File: maps
Created attachment 899663 [details] File: open_fds
Created attachment 899664 [details] File: proc_pid_status
Created attachment 899665 [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.