hardware-monitor crashed with SIGSEGV in g_signal_emit_valist()

Bug #761393 reported by Michael Mauch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
hardware-monitor (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: hardware-monitor

The crash happened when I logged in. I'm using Unity and the gnome-panel (so I can have a few applets) started from .config/autostart. Maybe the gnome-panel was not yet fully running? I also sometimes get messages that there was a problem loading applet X, Y or Z, so I guess maybe I'm doing something wrong here.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: hardware-monitor 1.4.2-1.1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
Date: Fri Apr 15 00:47:22 2011
ExecutablePath: /usr/lib/gnome-panel/hardware-monitor
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110408)
ProcCmdline: /usr/lib/gnome-panel/hardware-monitor --oaf-activate-iid=OAFIID:HardwareMonitor_Factory --oaf-ior-fd=25
ProcEnviron:
 LANG=de_DE.UTF-8
 LANGUAGE=de:en
 PATH=(custom, user)
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fd22af71dac <g_signal_emit_valist+940>: cmp 0x8(%rax),%rbx
 PC (0x7fd22af71dac) ok
 source "0x8(%rax)" (0x00000009) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: hardware-monitor
StacktraceTop:
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: hardware-monitor crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to natty on 2011-04-09 (6 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare
XsessionErrors: (nautilus:2258): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Michael Mauch (michael-mauch) wrote :
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

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

Other bug subscribers

Remote bug watches

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