Bug 439096 - Critical error when running gnome-system-monitor
Critical error when running gnome-system-monitor
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Søren Sandmann Pedersen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-26 18:38 EDT by petrosyan
Modified: 2014-06-18 05:10 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 06:33:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Desktop 533586 None None None Never

  None (edit)
Description petrosyan 2008-03-26 18:38:31 EDT
Description of problem:
Critical error when running gnome-system-monitor

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. start gnome-system-monitor from a terminal
2. go to 'Processes' tab
3. go to 'View/Memory Maps' or 'View/Open Files' menu item
Actual results:
$ gnome-system-monitor 

(gnome-system-monitor:3139): Gtk-CRITICAL **:
gtk_tree_selection_selected_foreach: assertion `GTK_IS_TREE_SELECTION
(selection)' failed

(gnome-system-monitor:3139): Gtk-CRITICAL **:
gtk_tree_selection_selected_foreach: assertion `GTK_IS_TREE_SELECTION
(selection)' failed

Expected results:
no critical errors
Comment 1 petrosyan 2008-04-23 22:40:01 EDT
this bug is still present in gnome-system-monitor-2.22.1-3.fc9.x86_64

this happens only when no process is selected from Process list. If I select any
process from the list then 'View/Memory Maps' or 'View/Open Files' menu items
work as expected.
Comment 2 Bug Zapper 2008-05-14 02:54:24 EDT
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
Comment 3 John Poelstra 2008-10-10 18:25:46 EDT
This bug has been triaged
Comment 4 Bug Zapper 2008-11-25 21:11:04 EST
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
Comment 5 Bug Zapper 2010-04-27 07:57:43 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  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 '11'.

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 11'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 11 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: 
Comment 6 Bug Zapper 2010-06-28 06:33:55 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.