Bug 651239 - [abrt] gnome-system-monitor-2.28.2-1.fc14: raise: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-system-monitor-2.28.2-1.fc14: raise: Process /usr/bin/gnome-syst...
Keywords:
Status: CLOSED DUPLICATE of bug 699076
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 14
Hardware: i686
OS: All
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ede054d213bd05942d0388c70fb...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 03:11 UTC by Hassan Latif
Modified: 2014-06-18 09:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-21 14:37:24 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (42.90 KB, text/plain)
2010-11-09 03:11 UTC, Hassan Latif 		no flags Details
View All

Description Hassan Latif 2010-11-09 03:11:30 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gnome-system-monitor
component: gnome-system-monitor
crash_function: raise
executable: /usr/bin/gnome-system-monitor
kernel: 2.6.35.6-48.fc14.i686
package: gnome-system-monitor-2.28.2-1.fc14
rating: 4
reason: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289229507
uid: 500
Comment 1 Hassan Latif 2010-11-09 03:11:34 UTC 
Created attachment 458954 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 14:37:24 UTC 
Backtrace analysis found this bug to be similar to bug #699076, closing as duplicate. This bug seems to belong to component gtk2, glib2, cairo, libXrender or libX11.

Bugs which were found to be similar to this bug: 
  emacs: bug #743059
  evolution: bug #710910
  gnome-system-monitor: bug #699061, bug #710654
  gnote: bug #699076
  libX11: bug #708271
  metacity: bug #677057

This comment is automatically generated.

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