gnome-system-monitor crashed with SIGSEGV in g_object_newv()

Bug #181676 reported by Jeremy Visser
28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gnome System Monitor
Fix Released
Critical
gnome-system-monitor (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-monitor

I have a dual-core system, and I like to have different colours for the two CPUs in the CPU History Resources graph. So, I dragged the light-blue coloured button from Network History onto the button for the second CPU. On Gutsy, this made the colour change properly. However, nothing changed. I then clicked on the colour button for the second CPU to manually change the colour, and the program crashed.

When the program restarted, the colour I had dragged onto the button in the first place was shown properly.

ProblemType: Crash
Architecture: amd64
Date: Thu Jan 10 14:09:28 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-system-monitor
NonfreeKernelModules: nvidia
Package: gnome-system-monitor 2.21.4-0ubuntu1
PackageArchitecture: amd64
ProcCmdline: gnome-system-monitor
ProcCwd: /home/jeremy
ProcEnviron:
 PATH=/home/jeremy/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=C
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-system-monitor
StacktraceTop:
 g_object_newv () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist ()
 g_object_new () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_type_create_instance ()
Title: gnome-system-monitor crashed with SIGSEGV in g_object_newv()
Uname: Linux rillian 2.6.24-3-generic #1 SMP Thu Jan 3 22:50:33 UTC 2008 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev scanner video
SegvAnalysis:
 Segfault happened at: 0x2ad3afea48e0 <g_object_newv+112>: mov (%rbx),%rsi
 PC (0x2ad3afea48e0) ok
 source "(%rbx)" (0xf2f2f2f20000) not located in a known VMA region (needed readable region)!
 destination "%rsi" ok
SegvReason: reading unknown VMA

Tags: apport-crash
Revision history for this message
Jeremy Visser (jeremy-visser) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_object_new_valist (object_type=6792624, first_property_name=0x0,
IA__g_object_new (object_type=6792624, first_property_name=0x0)
gtk_color_selection_init (colorsel=0xd58040)
IA__g_type_create_instance (type=47088699657680)
g_object_constructor (type=47088680140136, n_construct_properties=0,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in gnome-system-monitor:
importance: Undecided → Medium
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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

Changed in gnome-system-monitor:
assignee: nobody → desktop-bugs
status: New → Triaged
Revision history for this message
Jeremy Visser (jeremy-visser) wrote :

Thanks, mate. I wasn't sure if this was a duplicate or not.

Changed in gnome-system-monitor:
status: Unknown → New
Kees Cook (kees)
description: updated
Changed in gnome-system-monitor:
importance: Unknown → Critical
Changed in gnome-system-monitor:
status: New → Fix Released
Revision history for this message
Dmitri Bachtin (damg) wrote :

Original reporter has no suitable system to reproduce the bug.

This message is a call for testers: please verify whether the problem still persists.

Revision history for this message
Jeremy Visser (jeremy-visser) wrote :

I just tested this on my Natty + GNOME 3 PPA system, and could not reproduce it. I must say, if the bug were still present I would probably have reproduced this some other time.

Probably not worth wasting time on this one, and consider it accidentally fixed.

Revision history for this message
Dmitri Bachtin (damg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Oneiric Ocelot.

If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages.

Changed in gnome-system-monitor (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.