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
Started system up and received crash error for this.
Ubuntu Lucid Beta 1
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-18-generic i686
NonfreeKernelMo
Architecture: i386
Date: Wed Mar 31 23:23:30 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100325)
Lsusb:
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 064e:a101 Suyin Corp. Acer CrystalEye Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 7520
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: /usr/bin/
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.utf8
SegvAnalysis:
Segfault happened at: 0x10c400b: movsbl (%edx),%eax
PC (0x010c400b) 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:
dmi.bios.date: 12/21/2007
dmi.bios.vendor: Acer
dmi.bios.version: V1.21
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 7520
dmi.product.
dmi.sys.vendor: Acer
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.