Bug 972316 - [abrt] gnome-shell-3.8.2-3.fc19: tbl_B15: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
[abrt] gnome-shell-3.8.2-3.fc19: tbl_B15: Process /usr/bin/gnome-shell was ki...
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-06-08 06:59 EDT by Keith Burton
Modified: 2015-02-17 10:30 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 10:30:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (4.00 MB, text/plain)
2013-06-08 07:02 EDT, Keith Burton
no flags Details

  None (edit)
Description Keith Burton 2013-06-08 06:59:38 EDT
Description of problem:
Updated the latest updates via yum. Loged out then loged back in.
Error reported

Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        gnome-shell --mode=gdm
crash_function: tbl_B15
executable:     /usr/bin/gnome-shell
kernel:         3.9.4-301.fc19.x86_64
runlevel:       N 5
uid:            42

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 tbl_B15 at /usr/lib64/dri/swrast_dri.so
 #2 poll at ../sysdeps/unix/syscall-template.S:81
 #3 g_main_context_poll at gmain.c:3995
 #6 meta_run at core/main.c:556
Comment 1 Keith Burton 2013-06-08 07:02:27 EDT
Created attachment 758491 [details]
File: backtrace
Comment 2 ItSANgo 2013-07-18 21:42:13 EDT
When I login gnome-shell .

reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        gnome-shell --mode=gdm
crash_function: tbl_B15
executable:     /usr/bin/gnome-shell
kernel:         3.9.9-302.fc19.x86_64
package:        gnome-shell-3.8.3-3.fc19
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
reported_to:    uReport: BTHASH=d8cf9c9b5a474b6daf32b77b247d317b78727216
runlevel:       N 5
uid:            42
Comment 3 ItSANgo 2013-07-18 21:52:54 EDT
This problem resembles https://bugzilla.redhat.com/show_bug.cgi?id=979889 .
Comment 4 John William 2013-09-22 11:25:47 EDT
I can confirm that gnome-shell continues to crash frequently with the current gnome-shell-3.8.4-2.fc19 version.
Comment 5 Fedora End Of Life 2015-01-09 13:22:00 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 6 Fedora End Of Life 2015-02-17 10:30:23 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.