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
gnome-power-manager crashed during the screen blanking .
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Sat Apr 3 20:57:40 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
MachineType: Compaq Evo N620c (DE262A#ABU)
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
3.3V 32-bit PC Card
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=pl_PL.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xf2400b: movsbl (%edx),%eax
PC (0x00f2400b) 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: 05/02/2003
dmi.bios.vendor: Compaq
dmi.bios.version: 68BAF Ver. F.07
dmi.board.name: 0824
dmi.board.vendor: Compaq
dmi.board.version: 8051 Version 19.1D
dmi.chassis.type: 10
dmi.chassis.vendor: Compaq
dmi.modalias: dmi:bvnCompaq:
dmi.product.name: Evo N620c (DE262A#ABU)
dmi.product.
dmi.sys.vendor: Compaq
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 #552276, 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.