Bug 680638 - [abrt] gnome-system-monitor-2.28.2-1.fc14: _slope_compare: Process /usr/bin/gnome-system-monitor was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-system-monitor-2.28.2-1.fc14: _slope_compare: Process /usr/bin/g...
Keywords:
Status: CLOSED DUPLICATE of bug 674445
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7e1c5bce0b53b28d070628e8636...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-26 15:59 UTC by David
Modified: 2014-06-18 09:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:16:03 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (179.32 KB, text/plain)
2011-02-26 15:59 UTC, David 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description David 2011-02-26 15:59:35 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 183619 bytes
cmdline: gnome-system-monitor --show-system-tab
component: gnome-system-monitor
Attached file: coredump, 21831680 bytes
crash_function: _slope_compare
executable: /usr/bin/gnome-system-monitor
kernel: 2.6.35.11-83.fc14.i686
package: gnome-system-monitor-2.28.2-1.fc14
rating: 4
reason: Process /usr/bin/gnome-system-monitor was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298735821
uid: 500

How to reproduce
-----
1.
2.
3.
The program crashed while I was watching my system resources.
Comment 1 David 2011-02-26 15:59:38 UTC 
Created attachment 481159 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-20 18:16:03 UTC 
Backtrace analysis found this bug to be similar to bug #674445, closing as duplicate. This bug seems to belong to component gtk2, glib2 or cairo.

Bugs which were found to be similar to this bug: 
  abrt: bug #674444
  nautilus: bug #674445

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 674445 ***
Note You need to log in before you can comment on or make changes to this bug.