gnome-power-statistics crashed with SIGABRT in raise()

[Pete Graner]

Keeps crashing everytime I try and start it.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-power-manager 3.1.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 8 15:02:51 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-power-statistics
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110802.1)
MachineType: Dell Inc. Latitude XT2
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: /usr/bin/gnome-power-statistics
ProcCwd: /home/pgraner
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic root=UUID=8a31cf60-d703-45d7-b1f7-cc0197f59af0 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: gnome-power-manager
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
Title: gnome-power-statistics crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 05/05/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0K496P
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/05/2010:svnDellInc.:pnLatitudeXT2:pvr:rvnDellInc.:rn0K496P:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude XT2
dmi.sys.vendor: Dell Inc.
gnome-power-bugreport: Error: [Errno 2] No such file or directory

[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 #837354, 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.