gnome-power-manager crashed with SIGSEGV in clone()

[Attila Hammer]

Binary package hint: gnome-power-manager

This problem happens my Toshiba Satellite Pro L300 notebook when my battery level is 8%. Before ccrash this application, the battery level notification is displayed.

I hope helps this bugreport. I sent prewious this bugreport (yesterday), but unable to process because ttf-dejavu package is not installed (now installed latest version).

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-power-manager
Package: gnome-power-manager 2.24.0-0ubuntu14
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-power-manager
Stacktrace:
 #0 0xb5c302d8 in ?? ()
 #1 0xb6f663fe in clone () from /lib/tls/i686/cmov/libc.so.6
StacktraceTop:
 ?? ()
 clone () from /lib/tls/i686/cmov/libc.so.6
Title: gnome-power-manager crashed with SIGSEGV in clone()
Uname: Linux 2.6.28-6-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
clone () from /lib/tls/i686/cmov/libc.so.6

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Attila Hammer (hammera)]

Chris, I have one problem.
Trying backtracing crash problem with Pidgin application (another
bugreport). I using screen reader, but when I try debugging the
application, my screen reader not talking and don't no what happening.
Have another useful method back tracing my problem?

Attila

[Victor Vargas (kamus)]

Since this report have a long time without activity, could you check (if is possible) in latest version included in Karmic if this issue is still happening? Thanks in advance.

[xteejx (xteejx)]

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!