Bug 587323

Summary: [abrt] crash in gnome-system-monitor-2.28.0-3.fc12: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: sergeobelare
Component: gnome-system-monitorAssignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: kem, sandmann
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:5339098973aa7d5e8d83945382b7e1bb9ffce43b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-24 15:08:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description sergeobelare 2010-04-29 15:35:35 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: gnome-system-monitor
comment: May somehow be related to wireless going up and down, which is what I was monitoring.
component: gnome-system-monitor
executable: /usr/bin/gnome-system-monitor
global_uuid: 5339098973aa7d5e8d83945382b7e1bb9ffce43b
kernel: 2.6.32.11-99.fc12.i686
package: gnome-system-monitor-2.28.0-3.fc12
rating: 4
reason: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.Run system monitor
2.Resize to as small as it goes -- visible window, not totally minimized.
3. Let it run monitoring resources

Comment 1 sergeobelare 2010-04-29 15:35:37 UTC
Created attachment 410145 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-24 15:08:15 UTC

*** This bug has been marked as a duplicate of bug 571886 ***

Comment 3 Karel Klíč 2010-05-24 15:08:15 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 #571886.

Sorry for the inconvenience.