After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 480989 - gnome-system-monitor crashed with SIGSEGV
gnome-system-monitor crashed with SIGSEGV
Status: RESOLVED OBSOLETE
Product: system-monitor
Classification: Core
Component: general
2.20.x
Other Linux
: Normal critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-27 15:23 UTC by Sebastien Bacher
Modified: 2011-12-11 13:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sebastien Bacher 2007-09-27 15:23:20 UTC
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/144881

"Binary package hint: gnome-system-monitor

When I set its property on the 'Files System' (maybe, cause I use a Chinese version) tab, it crashed.
...
Package: gnome-system-monitor 2.20.0-0ubuntu1
...
  • #0 cb_update_disks
    at /usr/include/gdkmm-2.4/gdkmm/pixbuf.h line 277
  • #1 notify_listeners_callback
    at gconf-client.c line 2384
  • #2 gconf_listeners_notify
    at gconf-listeners.c line 589
  • #3 notify_one_entry
    at gconf-client.c line 2409
  • #4 notify_idle_callback
    at gconf-client.c line 2449
  • #5 g_idle_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 4132
  • #6 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #7 g_main_context_iterate
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #8 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #9 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.0/gtk/gtkmain.c line 1144

Comment 1 Benoît Dejean 2007-09-27 17:01:21 UTC
Do you actually have 24 mounted FS ?
Comment 2 Sebastien Bacher 2007-10-03 10:37:57 UTC
reply from the bug submitter

"I used`df` and show my fs as follows:
--------------------------------------------------------------------------------------------------------
/dev/hda3 9.2G 8.5G 248M 98% /
varrun 379M 88K 379M 1% /var/run
varlock 379M 0 379M 0% /var/lock
udev 379M 112K 379M 1% /dev
devshm 379M 0 379M 0% /dev/shm
lrm 379M 33M 347M 9%
/lib/modules/2.6.22-12-generic/volatile
/dev/hda7 12G 7.6G 3.8G 67% /media/hda8
/dev/hdb7 35G 29G 5.0G 86% /media/hdb7
/dev/hdb2 2.0G 1.7G 244M 88% /media/hdb2
/dev/hda1 7.8G 7.1G 790M 91% /media/hda1
/dev/hda5 17G 14G 3.1G 81% /media/hda5
/dev/hda6 16G 13G 3.2G 81% /media/hda6
/dev/hdb8 40G 37G 3.3G 92% /media/hdb8
/media/hda6/StudyResources/tmp_home_legion.img
                     1008M 353M 604M 37% /media/imgfs
none 379M 4.0K 379M 1% /media/ramfold
/dev/hdb6 36G 31G 4.8G 87% /media/hdb6
/dev/hdb5 36G 29G 7.6G 79% /media/hdb5
/dev/hda8 13G 9.6G 3.0G 77% /media/hda7
-----------------------------------------------------------------------------------------------------------"
Comment 3 Benoît Dejean 2007-10-03 14:17:22 UTC
OK, i don't get any segfault with 100 mounted FS, but when i change the properties not to display all FS, the virtual FS are incrementally removed for the disk list. This is wrong. Maybe there's a GtkTreeIter corruption somewhere.
Comment 4 Akhil Laddha 2010-12-28 04:48:18 UTC
Is this bug still valid in GNOME 2.30.2 or GNOME 2.32.1 ?
Comment 5 Chris Kühl 2011-12-11 13:53:21 UTC
I'm closing this due to lack of response. Reopen if still valid.