gnome-system-monitor crashed with SIGSEGV

[lert]

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.

ProblemType: Crash
Architecture: i386
Date: Wed Sep 26 01:47:20 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gnome-system-monitor
NonfreeKernelModules: cdrom
Package: gnome-system-monitor 2.20.0-0ubuntu1
PackageArchitecture: i386
ProcCmdline: gnome-system-monitor
ProcCwd: /media/hdb2/tmpHome/legion
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=zh_CN.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-system-monitor
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgconf-2.so.4
 ?? ()
 ?? ()
 ?? ()
Title: gnome-system-monitor crashed with SIGSEGV
Uname: Linux Zhengs-Computer 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom crontab dialout dip fax floppy fuse plugdev root scanner tape
SegvAnalysis:
 Segfault happened at: 0x8069197: mov (%edx),%eax
 PC (0x08069197) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA

[Apport retracing service (apport)]

StacktraceTop:notify_listeners_callback (listeners=0x80c5388, key=0x8451430 "/apps/procman/show_all_fs",
gconf_listeners_notify (listeners=0x80c5388,
notify_one_entry (client=0x80c0640, entry=0x83c0718) at gconf-client.c:2409
notify_idle_callback (data=0x80c0640) at gconf-client.c:2449
g_idle_dispatch (source=0x83e6db8, callback=0, user_data=0x80c0640)

[Sebastien Bacher (seb128)]

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=480989

[Sebastien Bacher (seb128)]

question from upstream, "Do you actually have 24 mounted FS ?"

[lert (lizheng02)]

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
-----------------------------------------------------------------------------------------------------------

2007/9/28, Sebastien Bacher <email address hidden>:
>
> question from upstream, "Do you actually have 24 mounted FS ?"
>
> --
> gnome-system-monitor crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/144881
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Niels Egberts (nielsegberts)]

I think I have the same problem as noted here but I am not 100% sure, my gnome-system-monitor also crashes when I select the tab file systems. I'm running Intrepid (gnome-system-monitor version 2.23.3-0ubuntu1).

I have filed a bug here: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/244903

[Niels Egberts (nielsegberts)]

My bug is fixed in Intrepid through some new updates.

[Niels Egberts (nielsegberts)]

Sorry, the bug is back here, it does not seem that an update is the cause so I think it was never fixt after all.

[Niels Egberts (nielsegberts)]

I'm sorry, my bug is back, it does not seem that an update is the cause so I think it was never fixt after all.

[Niels Egberts (nielsegberts)]

My bug is fixed in intrepid.

[Sokolov Sergey (cleversokol-deactivatedaccount)]

In Ubuntu 9.04 Alpha4 amd64 there is the same bug. I don't report a new one, because it's the same to this bug.

[Robert Roth (evfool)]

Thank you for reporting this bug to Ubuntu. 7.10 reached EOL on April 18th, 2009.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

I've tried recreating this bug with 12.10 and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

[dino99 (9d9)]

That version has died long ago; no more supported