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
Not sure why this happened. An error message just appeared.
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Thu Apr 1 19:36:55 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: TOSHIBA TOSHIBA NB200
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=en_GB.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7a500b: movsbl (%edx),%eax
PC (0x007a500b) 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 audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors: (polkit-
dmi.bios.date: 09/30/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V1.70
dmi.board.name: KAVAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: TOSHIBA NB200
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 #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.