Red Hat Bugzilla – Bug 586075
[abrt] crash in gnome-system-monitor-2.28.0-3.fc12: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Last modified: 2014-06-18 05:12:33 EDT
abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: gnome-system-monitor component: gnome-system-monitor executable: /usr/bin/gnome-system-monitor global_uuid: eefacae6ac5ef7c628d4012908c3d827ed79fb4d kernel: 2.6.32.10-90.fc12.x86_64 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)
Created attachment 409257 [details] File: backtrace
Package: gnome-system-monitor-2.28.0-3.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. Opened a .zip with file-roller 2. Opened System Monitor
*** Bug 539851 has been marked as a duplicate of this bug. ***
*** Bug 588078 has been marked as a duplicate of this bug. ***
*** Bug 589321 has been marked as a duplicate of this bug. ***
*** Bug 590326 has been marked as a duplicate of this bug. ***
*** Bug 590491 has been marked as a duplicate of this bug. ***
*** Bug 590867 has been marked as a duplicate of this bug. ***
*** Bug 591392 has been marked as a duplicate of this bug. ***
*** Bug 592097 has been marked as a duplicate of this bug. ***
*** Bug 592098 has been marked as a duplicate of this bug. ***
*** Bug 592675 has been marked as a duplicate of this bug. ***
*** Bug 592696 has been marked as a duplicate of this bug. ***
*** Bug 594955 has been marked as a duplicate of this bug. ***
*** Bug 594987 has been marked as a duplicate of this bug. ***
Package: gnome-system-monitor-2.28.0-3.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- Comment ----- I double check the icon of system monitor on my desktop accedently, and then it attemp to open two monitor. The first one starts correctly, but the sencond one crashes.
This is easily reproducible on F13 as per the description in comment 16.
Package: gnome-system-monitor-2.28.0-3.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1.system monitor consuming about 40% of cpu, so i pressed its window kill button (x) 2. 3.
Package: gnome-system-monitor-2.28.1-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- just opend manager from a hotkey
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
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.