Description of problem: This happened while I was away from the system. Might be related to the screen going dark after thirty mins. Version-Release number of selected component: gnome-shell-3.16.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: get_radeon_bo executable: /usr/bin/gnome-shell global_pid: 2083 kernel: 4.1.3-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 get_radeon_bo at radeon_drm_bo.c:90 #1 radeon_drm_get_cs_handle at radeon_drm_bo.c:823 #2 radeon_cs_create_fence at radeon_drm_cs.c:615 #3 radeon_drm_cs_flush at radeon_drm_cs.c:476 #4 si_context_gfx_flush at si_hw_context.c:104 #5 st_finish at state_tracker/st_cb_flush.c:98 #6 st_AllocTextureImageBuffer at state_tracker/st_cb_texture.c:521 #7 st_TexImage at state_tracker/st_cb_texture.c:875 #8 teximage at main/teximage.c:3364 #9 _mesa_TexImage2D at main/teximage.c:3403
Created attachment 1060854 [details] File: backtrace
Created attachment 1060855 [details] File: cgroup
Created attachment 1060856 [details] File: core_backtrace
Created attachment 1060857 [details] File: dso_list
Created attachment 1060858 [details] File: environ
Created attachment 1060859 [details] File: limits
Created attachment 1060860 [details] File: maps
Created attachment 1060861 [details] File: mountinfo
Created attachment 1060862 [details] File: namespaces
Created attachment 1060863 [details] File: open_fds
Created attachment 1060864 [details] File: proc_pid_status
Created attachment 1060865 [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.