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

[vasanag]

just tried to select power statistics

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-power-manager 3.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CasperVersion: 1.287
CrashCounter: 1
Date: Fri Oct 14 19:39:08 2011
ExecutablePath: /usr/bin/gnome-power-statistics
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Precision M4300
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: gnome-power-statistics
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/hostname.seed boot=casper persistent initrd=/casper/initrd.lz splash -- BOOT_IMAGE=/casper/vmlinuz
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 lpadmin nopasswdlogin sambashare
dmi.bios.date: 08/08/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0UY141
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd08/08/2007:svnDellInc.:pnPrecisionM4300:pvr:rvnDellInc.:rn0UY141:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M4300
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.