Bug 1051484

Summary: [abrt] gnome-shell: __bss_start(): Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Ryan <anyonguser>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: fmuellner, moez.roy, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2f250f3b53db139279edf5214c42cf0534c2233b
Whiteboard: abrt_hash:ce8fea4d3a26bf07a234fb55fac83f12d0710e67
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 14:19:38 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 Ryan 2014-01-10 11:57:08 UTC 
Description of problem:
The app would crash while been sat idle, Running inside virtual box 4.3

Version-Release number of selected component:
gnome-shell-3.10.2.1-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        gnome-shell --mode=gdm
crash_function: __bss_start
executable:     /usr/bin/gnome-shell
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            42

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 __bss_start at /usr/lib64/dri/swrast_dri.so
 #2 poll at /lib64/libc.so.6
 #3 g_main_context_iterate.isra.24 at /lib64/libglib-2.0.so.0
 #5 meta_run at /lib64/libmutter.so.0
Comment 1 Ryan 2014-01-10 11:57:13 UTC 
Created attachment 848141 [details]
File: backtrace
Comment 2 Ryan 2014-01-10 11:57:15 UTC 
Created attachment 848142 [details]
File: cgroup
Comment 3 Ryan 2014-01-10 11:57:17 UTC 
Created attachment 848143 [details]
File: core_backtrace
Comment 4 Ryan 2014-01-10 11:57:20 UTC 
Created attachment 848144 [details]
File: dso_list
Comment 5 Ryan 2014-01-10 11:57:21 UTC 
Created attachment 848145 [details]
File: environ
Comment 6 Ryan 2014-01-10 11:57:24 UTC 
Created attachment 848146 [details]
File: exploitable
Comment 7 Ryan 2014-01-10 11:57:26 UTC 
Created attachment 848147 [details]
File: limits
Comment 8 Ryan 2014-01-10 11:57:28 UTC 
Created attachment 848148 [details]
File: maps
Comment 9 Ryan 2014-01-10 11:57:30 UTC 
Created attachment 848149 [details]
File: open_fds
Comment 10 Ryan 2014-01-10 11:57:32 UTC 
Created attachment 848150 [details]
File: proc_pid_status
Comment 11 Ryan 2014-01-10 11:57:34 UTC 
Created attachment 848151 [details]
File: var_log_messages
Comment 12 Fedora End Of Life 2015-05-29 10:25:33 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 13 Fedora End Of Life 2015-06-29 14:19:38 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.