Bug 659055 - [abrt] crash in gnome-system-monitor-2.28.0-3.fc12: raise: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnome-system-monitor-2.28.0-3.fc12: raise: Process /usr/bin/g...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 12
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4ed46701fda696dd4826b2a2f82...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-01 20:12 UTC by tortasdefrijoles
Modified: 2014-06-18 09:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-03 11:56:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (12.30 KB, text/plain)
2010-12-01 20:12 UTC, tortasdefrijoles 		no flags Details
View All

Description tortasdefrijoles 2010-12-01 20:12:30 UTC 
abrt 1.1.1 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: 4ed46701fda696dd4826b2a2f82a2c088722fcae
kernel: 2.6.32.16-150.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.Left system monitor running for some time
2.
3.
Comment 1 tortasdefrijoles 2010-12-01 20:12:32 UTC 
Created attachment 464094 [details]
File: backtrace
Comment 2 Bug Zapper 2010-12-03 11:56:29 UTC 
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.
Note You need to log in before you can comment on or make changes to this bug.