[Intrepid] switching to the File Systems tab in GNOME System Monitor causes it to segfault

[Pramod Dematagoda]

Binary package hint: gnome-system-monitor

Whenever you attempt to switch to the File Systems tab in the GNOME System Monitor, it always segfaults, the messages log has:-
gnome-system-mo[20755]: segfault at 0 ip b764e9e5 sp bfcd2830 error 4 in libgiomm-2.4.so.1.0.25[b7611000+5e000]

While strace gives a more elaborate output which I will attach as a file.

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[Pramod Dematagoda (pmdematagoda)]

I tried using Apport(and it's on Intrepid, so it is on by default isn't it?) but it doesn't detect the crash at all. Also when I checked /var/crash, there was nothing in it either, is there anything else I can do? Thanks.

[Sebastien Bacher (seb128)]

get apport to work by opening a bug against it if required or attach a debug stacktrace using gdb

[Vikrant (vikrant82)]

I can confirm this. I have upgraded from Hardy to Intrepid alpha 1.

[Pramod Dematagoda (pmdematagoda)]

One more thing, this segmentation fault does not occur when only the partitions mounted at boot are mounted, if however another partition/drive is mounted then System Monitor loses it and starts segfaulting.

So this problem is not related to the File System tab.

[Pramod Dematagoda (pmdematagoda)]

I managed to figure out gdb, and I am attaching the output given by it.

[Pedro Villavicencio (pedro)]

looks like http://bugzilla.gnome.org/show_bug.cgi?id=529533 , Pramod can you get a detailed stack trace? just follow the instructions at https://wiki.ubuntu.com/Backtrace

[Pramod Dematagoda (pmdematagoda)]

It does look like the Bugzilla report.

[Pramod Dematagoda (pmdematagoda)]

I should mention, the stack trace attached has both the abnormal trace(the first one) and the normal trace(the last one).

[Pedro Villavicencio (pedro)]

ok that's a glibmm issue, re assign it.

[Pedro Villavicencio (pedro)]

also it's a dup of bug 231647