Bug 613723 - [abrt] crash in gnome-system-monitor-2.28.1-1.fc13: raise: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-system-monitor-2.28.1-1.fc13: raise: Process /usr/bin/g...
Keywords:
Status: CLOSED DUPLICATE of bug 625196
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1cab53eed8c36b5e2b26c5302d8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-12 17:05 UTC by Jorge
Modified: 2014-06-18 09:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:41:10 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (11.77 KB, text/plain)
2010-07-12 17:05 UTC, Jorge 		no flags Details
View All

Description Jorge 2010-07-12 17:05:01 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gnome-system-monitor
comment: Not sure what happened, think the DVD player hung on a crap DVD and was missing/queing the subsequent mouse clicks which led to this crash.
component: gnome-system-monitor
crash_function: raise
executable: /usr/bin/gnome-system-monitor
global_uuid: 1cab53eed8c36b5e2b26c5302d8257fc3dff7ca4
kernel: 2.6.33.6-147.fc13.x86_64
package: gnome-system-monitor-2.28.1-1.fc13
rating: 4
reason: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Jorge 2010-07-12 17:05:04 UTC 
Created attachment 431216 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:41:10 UTC 

*** This bug has been marked as a duplicate of bug 625196 ***
Comment 3 Karel Klíč 2010-11-08 19:41:10 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 #625196.

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