Bug 1101716

Summary: [abrt] gnome-shell: get_radeon_bo(): gnome-shell killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Flóki Pálsson <flokip>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0667d701ead6ee34ee9fae08eee191e5ebcd64b1
Whiteboard: abrt_hash:da6efefdbffdd2170170b54039ffa6eb65fc8c4b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:33:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Flóki Pálsson 2014-05-27 19:06:04 UTC 
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
Comment 1 Flóki Pálsson 2014-05-27 19:06:08 UTC 
Created attachment 899655 [details]
File: backtrace
Comment 2 Flóki Pálsson 2014-05-27 19:06:09 UTC 
Created attachment 899656 [details]
File: cgroup
Comment 3 Flóki Pálsson 2014-05-27 19:06:11 UTC 
Created attachment 899657 [details]
File: core_backtrace
Comment 4 Flóki Pálsson 2014-05-27 19:06:12 UTC 
Created attachment 899658 [details]
File: dso_list
Comment 5 Flóki Pálsson 2014-05-27 19:06:14 UTC 
Created attachment 899659 [details]
File: environ
Comment 6 Flóki Pálsson 2014-05-27 19:06:15 UTC 
Created attachment 899660 [details]
File: exploitable
Comment 7 Flóki Pálsson 2014-05-27 19:06:16 UTC 
Created attachment 899661 [details]
File: limits
Comment 8 Flóki Pálsson 2014-05-27 19:06:18 UTC 
Created attachment 899662 [details]
File: maps
Comment 9 Flóki Pálsson 2014-05-27 19:06:19 UTC 
Created attachment 899663 [details]
File: open_fds
Comment 10 Flóki Pálsson 2014-05-27 19:06:20 UTC 
Created attachment 899664 [details]
File: proc_pid_status
Comment 11 Flóki Pálsson 2014-05-27 19:06:22 UTC 
Created attachment 899665 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:50:56 UTC 
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
Comment 13 Fedora End Of Life 2016-07-19 11:33:59 UTC 
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.