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

[spydouglas]

Binary package hint: gnome-power-manager

The battery was low when it crashed.

ProblemType: Crash
ACAdapter: Present
Architecture: powerpc
Battery: Present
CPUScaling: Present
Disassembly: 0xd5ff270:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-power-manager
LaptopPanel: Present
Package: gnome-power-manager 2.24.2-2ubuntu7
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-power-manager
Stacktrace:
 #0 0x0d5ff270 in ?? ()
 #1 0x0f1757dc in __nptl_deallocate_tsd () from /lib/libpthread.so.0
 #2 0x0f176e9c in start_thread () from /lib/libpthread.so.0
 #3 0x0f0d1ee0 in clone () from /lib/libc.so.6
 Backtrace stopped: previous frame inner to this frame (corrupt stack?)
StacktraceTop:
 ?? ()
 __nptl_deallocate_tsd () from /lib/libpthread.so.0
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
Title: gnome-power-manager crashed with SIGSEGV in __nptl_deallocate_tsd()
Uname: Linux 2.6.28-6-powerpc ppc
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:?? ()
__nptl_deallocate_tsd () from /lib/libpthread.so.0
start_thread () from /lib/libpthread.so.0
clone () from /lib/libc.so.6

[Scott Howard (showard314)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually 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.

[Boniek (boniek12p)]

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!