Ubuntu
gnome-power-manager package

gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #433379 reported by tuxracer on 2009-09-20

This bug report is a duplicate of: Bug #431023: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	gnome-power-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: gnome-power-manager

Random crash

ProblemType: Crash
Architecture: i386
CheckboxSubmission: 059a992a96abf6e3ee6c3537ba217ecb
CheckboxSystem: d043ff9530fa282594d25d5b680908f1
Date: Sun Sep 20 00:22:02 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
Package: gnome-power-manager 2.27.92-0ubuntu1
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SegvAnalysis:
Segfault happened at: 0x8053413: mov 0x8(%eax),%eax
PC (0x08053413) ok
source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
?? ()
?? ()
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

tuxracer (tuxracer) wrote on 2009-09-20:

DevkitPower.txt Edit (1.5 KiB, text/plain; charset="utf-8")
GConfNonDefault.txt Edit (884 bytes, text/plain; charset="utf-8")
gnome-power-bugreport.txt Edit (4.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-20: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #431023, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.