Bug 586082 - [abrt] crash in metacity-2.28.0-14.fc12: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in metacity-2.28.0-14.fc12: Process /usr/bin/metacity was killed...
Status: CLOSED DUPLICATE of bug 540129
Alias: None
Product: Fedora
Classification: Fedora
Component: metacity   
(Show other bugs)
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6666d30c76fc4e0b769a2ea3ca7...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 18:57 UTC by BobbyD_FL
Modified: 2010-05-25 10:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-25 10:00:35 UTC
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 (25.83 KB, text/plain)
2010-04-26 18:57 UTC, BobbyD_FL 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description BobbyD_FL 2010-04-26 18:57:36 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: metacity
component: metacity
executable: /usr/bin/metacity
global_uuid: 6666d30c76fc4e0b769a2ea3ca7633c1d767718a
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: metacity-2.28.0-14.fc12
rating: 4
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 BobbyD_FL 2010-04-26 18:57:37 UTC 
Created attachment 409261 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:00:35 UTC 

*** This bug has been marked as a duplicate of bug 540129 ***
Comment 3 Karel Klíč 2010-05-25 10:00:35 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #540129.

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