Bug 612897 – [abrt] crash in metacity-2.28.0-9.fc12: Process was terminated by signal 11

Bug 612897 - [abrt] crash in metacity-2.28.0-9.fc12: Process was terminated by signal 11

Summary:	[abrt] crash in metacity-2.28.0-9.fc12: Process was terminated by signal 11

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	metacity (Show other bugs)
Sub Component:
Version:	12
Hardware:	x86_64 Linux

Priority	low Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Owen Taylor
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:	abrt_hash:c613404e825466d6f90b9577ef9...
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-07-09 06:41 EDT by colinmw
Modified:	2010-07-09 13:23 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2010-07-09 13:23:53 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
File: backtrace (5.87 KB, text/plain) 2010-07-09 06:41 EDT, colinmw	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description colinmw 2010-07-09 06:41:40 EDT

abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: metacity
component: metacity
executable: /usr/bin/metacity
global_uuid: c613404e825466d6f90b9577ef9b7ef0cc29d17f
kernel: 2.6.31.5-127.fc12.x86_64
package: metacity-2.28.0-9.fc12
rating: 0
reason: Process was terminated by signal 11
release: Fedora release 12 (Constantine)

Comment 1 colinmw 2010-07-09 06:41:42 EDT

Created attachment 430599 [details]
File: backtrace

Comment 2 Owen Taylor 2010-07-09 13:23:53 EDT

Unfortunately, the back trace in this bug report has no useful information it (the crash reporting tool was unable to get the debug symbols), so there's nothing I can do with it. Thanks anyways for taking the time to report the crash.

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