Bug 689160 - [abrt] gnome-shell-2.91.91-2.fc15: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-shell-2.91.91-2.fc15: Process /usr/bin/gnome-shell was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 680537
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1f362332ad86224ca97d96df086...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-20 00:50 UTC by James Cape
Modified: 2011-03-26 16:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-26 16:15:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.60 KB, text/plain)
2011-03-20 00:50 UTC, James Cape 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description James Cape 2011-03-20 00:50:45 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 29288 bytes
cmdline: /usr/bin/gnome-shell
component: gnome-shell
Attached file: coredump, 283222016 bytes
crash_function: _cogl_pipeline_set_layer_texture_target
executable: /usr/bin/gnome-shell
kernel: 2.6.38-1.fc15.x86_64
package: gnome-shell-2.91.91-2.fc15
rating: 4
reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1300582147
uid: 500

How to reproduce
-----
1. Double-clicked on the Banshee titlebar to maximize
2. Things appeared to be "stuck"
3. Hit Meta
4. Crash.
Comment 1 James Cape 2011-03-20 00:50:48 UTC 
Created attachment 486425 [details]
File: backtrace
Comment 2 Jon Dufresne 2011-03-21 04:50:47 UTC 
Package: gnome-shell-2.91.91-2.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. Nothing special
2.
3.
Comment 3 Owen Taylor 2011-03-26 16:15:54 UTC 

*** This bug has been marked as a duplicate of bug 680537 ***
Note You need to log in before you can comment on or make changes to this bug.