gnome-system-monitor crashes on startup

[Dylan Borg]

I try to start system-monitor and it crashes on startup i.e. no window is displayed. On the terminal a crash message is shown.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-system-monitor 3.3.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-16.25-generic-pae 3.2.6
Uname: Linux 3.2.0-16-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 18 16:13:38 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: gnome-system-monitor
UpgradeStatus: Upgraded to precise on 2012-02-13 (5 days ago)

[Dylan Borg (borgdylan)]

dylan@ubuntu-server:~/Desktop$ gnome-system-monitor

GLib-CRITICAL **: g_variant_get_child_value: assertion `index_ < g_variant_n_children (value)' failed

GLib-CRITICAL **: g_variant_get_va: assertion `value != NULL' failed

GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
*** glibc detected *** gnome-system-monitor: double free or corruption (fasttop): 0x085b4268 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x72ae2)[0xb6475ae2]
/lib/i386-linux-gnu/libglib-2.0.so.0(+0x4cbeb)[0xb673ebeb]
/lib/i386-linux-gnu/libglib-2.0.so.0(g_free+0x20)[0xb673ed60]
gnome-system-monitor[0x805b372]
gnome-system-monitor[0x805c869]
gnome-system-monitor(main+0x24b)[0x805979b]
/lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3)[0xb641c4d3]
gnome-system-monitor[0x805ae09]
======= Memory map: ========
08048000-0808a000 r-xp 00000000 08:02 5374472 /usr/bin/gnome-system-monitor
0808a000-0808b000 r--p 00041000 08:02 5374472 /usr/bin/gnome-system-monitor
0808b000-0808c000 rw-p 00042000 08:02 5374472 /usr/bin/gnome-system-monitor
0808c000-0808d000 rw-p 00000000 00:00 0
084d4000-085f9000 rw-p 00000000 00:00 0 [heap]
b4700000-b4800000 ---p 00000000 00:00 0
b48ff000-b4900000 ---p 00000000 00:00 0
b4900000-b5100000 rw-p 00000000 00:00 0
b5100000-b5121000 rw-p 00000000 00:00 0
b5121000-b5200000 ---p 00000000 00:00 0
b52d1000-b52d2000 ---p 00000000 00:00 0
b52d2000-b5ad2000 rw-p 00000000 00:00 0
b5ad2000-b5af9000 r--p 00000000 08:02 6424152 /usr/share/glib-2.0/schemas/gschemas.compiled
b5af9000-b5afd000 r-xp 00000000 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
b5afd000-b5afe000 r--p 00003000 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
b5afe000-b5aff000 rw-p 00004000 08:02 5385163 /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
b5aff000-b5b1f000 r--s 00000000 08:02 5899997 /usr/share/mime/mime.cache
b5b1f000-b5b2e000 r-xp 00000000 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so
b5b2e000-b5b2f000 r--p 0000e000 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so
b5b2f000-b5b30000 rw-p 0000f000 08:02 5374409 /usr/lib/gtk-3.0/3.0.0/theming-engines/libunico.so
b5b30000-b5b3e000 r-xp 00000000 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0
b5b3e000-b5b3f000 r--p 0000e000 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0
b5b3f000-b5b40000 rw-p 0000f000 08:02 38015979 /lib/i386-linux-gnu/libudev.so.0.13.0
b5b40000-b5b87000 r-xp 00000000 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8
b5b87000-b5b88000 r--p 00046000 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8
b5b88000-b5b89000 rw-p 00047000 08:02 38011837 /lib/i386-linux-gnu/libdbus-1.so.3.5.8
b5b90000-b5b91000 r--p 00000000 08:02 7216147 /usr/share/locale-langpack/en_GB/LC_MESSAGES/gdk-pixbuf.mo
b5b9e000-b5b9f000 rw-p 00000000 00:00 0
b5b9f000-b5ba8000 r--p 00000000 08:02 57947479 /home/dylan/.config/dconf/user
b5ba8000-b5ba9000 r--s 00000000 08:02 57947454 /home/dylan/.cache/dconf/user
b5ba9000-b5bb0000 r-xp 00000000 08:02 5377868 /usr/lib/i386-linux-...

[Vadim Rutkovsky (roignac)]

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.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

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.

[Dylan Borg (borgdylan)]

No crash file is made in /var/crash so I cannot report a bug with it!!

[Dylan Borg (borgdylan)]

This only happens on computer with more than 4 threads in the CPU. To fix set the cpu-colors variable to
[(0, '#FF6E00'), (1, '#CB0C29'), (2, '#49A835'), (3, '#2D7DB3'), (4, '#FF6E00'), (5, '#CB0C29'), (6, '#49A835'), (7, '#2D7DB3')]
in org->gnome->gnome-system-monitor by using dconf-editor.

[Vadim Rutkovsky (roignac)]

Please enable apport in /etc/default/apport, restart gnome-system-monitor and report the issue using apport

[Dylan Borg (borgdylan)]

Apport is enabled as Im using precise.

[Vadim Rutkovsky (roignac)]

Could you please try running '/usr/share/apport/apport-gtk' and try
filing a new bug with stacktrace information?

[Sebastien Bacher (seb128)]

the issue described there seems to be fixed in git, http://git.gnome.org/browse/gnome-system-monitor/commit/?id=6e966d0cfca266d5f1ea02995b7debc198ff636d and the fix will be in the next version