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

Bug #716355 reported by Jean-Baptiste Lallement on 2011-02-10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)

Bug Description

Binary package hint: gnome-system-monitor

Occurred during automated desktop testing.
The application crashed at start.
This is not reproducible

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-system-monitor 2.28.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-2.29-generic 2.6.38-rc3
Uname: Linux 2.6.38-2-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Feb 10 11:12:21 2011
ExecutablePath: /usr/bin/gnome-system-monitor
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110202)
ProcCmdline: gnome-system-monitor
 Segfault happened at: 0x7fcca85756a4 <g_type_parent+20>: mov 0x50(%rdi),%rax
 PC (0x7fcca85756a4) ok
 source "0x50(%rdi)" (0xfffffffff14e4e9c) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-system-monitor
 g_type_parent () from /usr/lib/
 g_signal_emit_by_name () from /usr/lib/
 ?? () from /usr/lib/gtk-2.0/modules/
 ?? () from /usr/lib/
 g_main_context_dispatch () from /lib/
Title: gnome-system-monitor crashed with SIGSEGV in g_type_parent()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Jean-Baptiste Lallement (jibel) wrote :
Patrick Wright (patrickmwright) wrote :

Mago test passes with Beta 2 installation

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

Other bug subscribers