gnome-power-manager crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
The power manager recently stopped working. It will suspend or hibernate OK but then will not restart. I ned to turn off my Dell 9150 Desktop and reboot.
Maverick Meerkat Beta. Stopped about two weeks ago.
Workaround don't suspend or hibernate, leave system running or turn off.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.92-0ubunntu1
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Fri Sep 24 09:55:34 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
MachineType: Dell Inc. Dell DXP051
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: gnome-power-manager
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x10144fb: movsbl (%edx),%eax
PC (0x010144fb) ok
source "(%edx)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: gnome-power-manager crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/01/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 0YC523
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Dell DXP051
dmi.sys.vendor: Dell Inc.
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 #644360, 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.