Bug 691915 - [abrt] gnome-shell-2.91.92-3.fc15: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-shell-2.91.92-3.fc15: Process /usr/bin/gnome-shell was killed by...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:(null)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 20:59 UTC by STEVEN WARD
Modified: 2011-03-29 21:15 UTC (History)
4 users (show)

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


Attachments (Terms of Use)
File: event_log (19.99 KB, text/plain)
2011-03-29 20:59 UTC, STEVEN WARD
no flags Details

Description STEVEN WARD 2011-03-29 20:59:48 UTC
abrt version: 2.0.0
executable: /usr/bin/gnome-shell
cmdline: /usr/bin/gnome-shell
component: gnome-shell
architecture: i686
kernel: 2.6.38.1-6.fc15.i686
reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
package: gnome-shell-2.91.92-3.fc15
uid: 500
time: 1301217966

Text file: event_log, 20469 bytes
Binary file: coredump, 104800256 bytes

comment
-----
Logged into the latest kernel and updates from 29-03-11 on Fedora 15 Alpha.
Logged into Gnome via GDM.
Wait for the Desktop to appear when logging in.

description
-----
Window management and application launching for GNOME

GNOME Shell provides core user interface functions for the GNOME 3 desktop,
like switching to windows and launching applications. GNOME Shell takes
advantage of the capabilities of modern graphics hardware and introduces
innovative user interface concepts to provide a visually attractive and
easy to use experience.

Comment 1 STEVEN WARD 2011-03-29 20:59:52 UTC
Created attachment 488574 [details]
File: event_log

Comment 2 Owen Taylor 2011-03-29 21:15:26 UTC
Unfortunately ABRT failed to get a backtrace here, so there's nothing we can really do further to figure out what happened.


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