--
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
-
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.92-0ubunntu1 [modified: usr/bin/
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CheckboxSubmission: c55f9df3c413f60
CheckboxSystem: c541d13ea4f205f
CrashCounter: 1
Date: Thu Sep 23 01:37:09 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
MachineType: TOSHIBA Satellite L305
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: gnome-power-manager
ProcCwd: /home/user
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
LANGUAGE=en_US:en
SegvAnalysis:
Segfault happened at: 0xea34fb: movsbl (%edx),%eax
PC (0x00ea34fb) ok
source "(%edx)" (0x00000284) 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
XsessionErrors:
(polkit-
(bluetooth-
(gnome-
(nautilus:1807): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
dmi.bios.date: 12/09/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 2.20
dmi.board.
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: Satellite L305
dmi.product.
dmi.sys.vendor: TOSHIBA
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.