GNOME Bugzilla – Bug 533586
Critical error when running gnome-system-monitor
Last modified: 2011-11-11 10:03:55 UTC
Please describe the problem: Critical error when running gnome-system-monitor Version-Release number of gnome-system-monitor: gnome-system-monitor-2.22.1-5.fc9.x86_64 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:4185): Gtk-CRITICAL **: gtk_tree_selection_selected_foreach: assertion `GTK_IS_TREE_SELECTION (selection)' failed (gnome-system-monitor:4185): Gtk-CRITICAL **: gtk_tree_selection_selected_foreach: assertion `GTK_IS_TREE_SELECTION (selection)' failed Expected results: no critical errors Does this happen every time? Yes Other information: 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.
I seem to have the same error, I even can't select the "processes" tab (starting it by clicking the applet). The bug-buddy info: Distribution: Gentoo Base System release 1.12.11.1 Gnome Release: 2.22.3 2008-08-18 (Gentoo) BugBuddy Version: 2.22.0 System: Linux 2.6.25-gentoo-r7 #4 Sun Aug 31 11:16:59 CEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: ClearlooksClassic Icon Theme: gnome Memory status: size: 41201664 vsize: 41201664 resident: 16965632 share: 13766656 rss: 16965632 rss_rlim: 4294967295 CPU usage: start_time: 1222355868 rtime: 57 utime: 44 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-system-monitor' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6a83960 (LWP 4490)] 0xb7fa7424 in __kernel_vsyscall ()
+ Trace 207318
Thread 1 (Thread 0xb6a83960 (LWP 4490))
----------- .xsession-errors (2451 sec old) --------------------- project data set for /home/admin/Source/c++/!rp/fractal/fformat.h project data set for /home/admin/Source/c++/!rp/fractal/fformat.cpp project data set for /home/admin/Source/c++/!rp/fractal/gui.h project data set for /home/admin/Source/c++/!rp/fractal/gui.cpp project data set for /home/admin/Source/c++/!rp/fractal/headers.h project data set for /home/admin/Source/c++/!rp/fractal/main.cpp project data set for /home/admin/Source/c++/!rp/fractal/compress.cpp Top Editor: /home/admin/Source/c++/!rp/fractal/blocks.cpp Add project RP-FIC in parsing queue Caching internal gcc dirs for adding to parser... Caching GCC dir: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4 Caching GCC dir: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/g++-v4/i686-pc-linux-gnu Caching GCC dir: /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include/gWindow manager warning: Invalid WM_TRANSIENT_FOR window 0x3400007 specified for 0x34002c1 (Settings: ). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3400007 specified for 0x340048f (Settings: ). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3400007 specified for 0x34005ca (Settings: ). -------------------------------------------------- Is the trace of some use, or do I have to debug glibc as well? Good luck. (I'm debugging my own app and it's really driving me mad :-)
Seems that this has been fixed in the meantime. Please reopen if that's not the case.