gnome-power-manager crashed with SIGSEGV

[joelw135]

Binary package hint: gnome-power-manager

Screensaver crashes when screen goes blank.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-power-manager 2.30.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
CheckboxSubmission: 80e945698fd22f2c605dbf229843c951
CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32
CrashCounter: 1
Date: Wed Mar 31 13:54:45 2010
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
MachineType: Dell Inc. Dell DM051
ProcCmdLine: root=UUID=4841fe4c-b67a-44b7-9cc0-6080972f1ff3 ro quiet splash
ProcCmdline: /usr/bin/gnome-power-manager
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
SegvAnalysis:
 Segfault happened at: 0x102d00b: movsbl (%edx),%eax
 PC (0x0102d00b) 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/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare
dmi.bios.date: 10/13/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A02
dmi.board.name: 0WG261
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/13/2005:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0WG261:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: Dell DM051
dmi.sys.vendor: Dell Inc.

[Apport retracing service (apport)]

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.