desktop-packages team mailing list archive

[Dmitri Bachtin <181676@xxxxxxxxxxxxxxxxxx>]

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/181676

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

Status in The GNOME System Monitor:
  Fix Released
Status in “gnome-system-monitor” package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-system-monitor/+bug/181676/+subscriptions