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 'crash' icon appear at start up...
Everything seems to work.
The computer is a HP DV9000 laptop.
Thanks
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
NonfreeKernelMo
Architecture: i386
CurrentDmesg:
[ 20.646957] ppdev: user-space parallel port driver
[ 28.928023] eth1: no IPv6 routers present
[ 84.504051] Clocksource tsc unstable (delta = -181195450 ns)
[ 392.228031] CE: hpet increasing min_delta_ns to 15000 nsec
Date: Thu Apr 1 09:43:04 2010
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318)
MachineType: Hewlett-Packard HP Pavilion dv9500 Notebook PC
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=fr_CA.utf8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xf3000b: movsbl (%edx),%eax
PC (0x00f3000b) 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: 01/21/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.28
dmi.board.name: 30D1
dmi.board.vendor: Quanta
dmi.board.version: 85.24
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv9500 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.