gnome-power-manager crashed with SIGSEGV

Bug #646761 reported by Philip Peitsch on 2010-09-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)

Bug Description

Binary package hint: gnome-power-manager

This just happened out of the blue... I have no idea how to reproduce

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.92-0ubunntu1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: wl
Architecture: i386
Date: Fri Sep 24 21:59:35 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
MachineType: Acer AOD260
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=96a46ef1-42bb-4cc0-a6d3-118f5b77c38c ro quiet splash
ProcCmdline: gnome-power-manager
 Segfault happened at: 0x11014fb: movsbl (%edx),%eax
 PC (0x011014fb) 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
 ?? () 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 06/04/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.06
dmi.board.asset.tag: Base Board Asset Tag AOD260
dmi.board.vendor: Acer
dmi.board.version: V1.06
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.06
dmi.modalias: dmi:bvnAcer:bvrV1.06:bd06/04/2010:svnAcer:pnAOD260:pvrV1.06:rvnAcer:rnAOD260:rvrV1.06:cvnAcer:ct10:cvrV1.06: AOD260
dmi.product.version: V1.06
dmi.sys.vendor: Acer

Philip Peitsch (philip-peitsch) wrote :

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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers