Bug 592675 - [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 586075
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c8c3f1e65707bfe2087c795323f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-16 07:13 UTC by Igor Katalnikov
Modified: 2014-06-18 09:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:22:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (8.45 KB, text/plain)
2010-05-16 07:13 UTC, Igor Katalnikov 		no flags Details
View All

Description Igor Katalnikov 2010-05-16 07:13:19 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-system-monitor
component: gnome-system-monitor
crash_function: raise
executable: /usr/bin/gnome-system-monitor
global_uuid: c8c3f1e65707bfe2087c795323f1facf12a9d32a
kernel: 2.6.33.3-85.fc13.i686.PAE
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)

How to reproduce
-----
1. Accidentaly dubbelclick on system monitor applet.
2.First system monitor fails
3. second system monitor opens
Comment 1 Igor Katalnikov 2010-05-16 07:13:21 UTC 
Created attachment 414316 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:22:38 UTC 

*** This bug has been marked as a duplicate of bug 586075 ***
Comment 3 Karel Klíč 2010-05-25 09:22:38 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 #586075.

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