gnome-power-statistics crashed with SIGSEGV in __libc_start_main()

[Juan Sebastián Marulanda]

Binary package hint: gnome-power-manager

I get this error while trying to get the power history from the power tray icon.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Aug 20 13:07:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-statistics
Package: gnome-power-manager 2.27.5-0ubuntu2
ProcCmdline: /usr/bin/gnome-power-statistics
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-6.25-generic-pae
SegvAnalysis:
 Segfault happened at: 0x8051166 <cairo_move_to@plt+17114>: mov (%eax),%edi
 PC (0x08051166) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
Stacktrace:
 #0 0x08051166 in ?? ()
 #1 0xb762cb56 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #2 0x0804cec1 in ?? ()
StacktraceTop:
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (Thread 4946):
 #0 0x08051166 in ?? ()
 #1 0xb762cb56 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #2 0x0804cec1 in ?? ()
Title: gnome-power-statistics crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.31-6-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Apport retracing service (apport)]

StacktraceTop:main (argc=1, argv=0xbf90c594) at gpm-statistics.c:1725

[Steve Beattie (sbeattie)]

Thank you for taking the time report this issue and help improve Ubuntu. I am unable to reproduce this issue; however, I do note that gnome-power-manager 2.27.91-0ubuntu1 was uploaded on 2009-08-26. Are you still seeing this crash when you attempt to view the power history? Thanks!

[Juan Sebastián Marulanda (juanchito2006)]

It still crashes as of the latest version.

[Nicolas DERIVE (kalon33)]

It happens on my computer latest updated from now which do not have a battery. Maybe is it an hint to find the bug ?

[David Tombs (dgtombs)]

Confirming as reporter has provided necessary information.

[Pedro Villavicencio (pedro)]

Thanks for the report Juan Sebastián Marulanda , It has been a long time without any comment or a duplicate in this bug report and It is possible that the bug has been fixed. May you please try to reproduce it with the latest Stable Release of Ubuntu the Natty Narwhal and add the respective comments to the report? You can learn how to get that release at http://www.ubuntu.com/download . Thanks again and we appreciate your help.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!