GNOME Bugzilla – Bug 631208
crash in System Monitor: Openning the 'File Syste...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.28.1 What were you doing when the application crashed? Openning the 'File Systems' tab in 'System Monitor Preferences' Distribution: Gentoo Base System release 1.12.13 Gnome Release: 2.30.2 2010-09-04 (Gentoo) BugBuddy Version: 2.30.0 System: Linux 2.6.30-tuxonice-r6 #10 SMP Fri Sep 24 23:24:16 EEST 2010 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaBlu Icon Theme: gnome-alternative GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 85647360 vsize: 85647360 resident: 19484672 share: 15884288 rss: 19484672 rss_rlim: 18446744073709551615 CPU usage: start_time: 1286084954 rtime: 251 utime: 173 stime: 78 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-system-monitor' [Thread debugging using libthread_db enabled] 0xb80d8424 in __kernel_vsyscall ()
+ Trace 223987
Thread 1 (Thread 0xb6858a50 (LWP 11253))
Inferior 1 [process 11253] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (42052 sec old) --------------------- (gxine:8209): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel Debug: Playlist::maybeSaveSettings Debug: Playlist::maybeSaveSettings Debug: Playlist::maybeSaveSettings Debug: Playlist::maybeSaveSettings (gxine:8209): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel (gxine:8209): Gdk-WARNING **: gdk_window_set_user_time called on non-toplevel ...Too much output, ignoring rest... --------------------------------------------------
I have changed the update interval in 'Resource' tab before switching to 'File Systems' tab. The bug is nicely reproducible.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 578520 ***