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

[nigroller]

Binary package hint: gnome-power-manager

Crashed when the power cable was unplugged

ProblemType: Crash
ACAdapter: Present
Architecture: amd64
Battery: Present
CPUScaling: Present
CrashCounter: 1
Disassembly: 0x7f65083d4610:
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-power-manager
LaptopPanel: Present
Package: gnome-power-manager 2.24.2-2ubuntu8
ProcCmdline: gnome-power-manager
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-power-manager
Stacktrace:
 #0 0x00007f65083d4610 in ?? ()
 #1 0x00007f6515686459 in start_thread () from /lib/libpthread.so.0
 #2 0x00007f65153f2fcd in clone () from /lib/libc.so.6
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 ?? ()
 start_thread () from /lib/libpthread.so.0
 clone () from /lib/libc.so.6
 ?? ()
Title: gnome-power-manager crashed with SIGSEGV in start_thread()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev pulse-access pulse-rt sambashare

[Apport retracing service (apport)]

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

[Andreas Moog (ampelbein)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

[nigroller (nigroller)]

It happened when I was playing Stronghold with wine 1.1.18. Wine was compiled by myself (I believe the changeset/revision number is f212579ae9a1b770ebd34cec20f95e1977bb57f0). Today I managed to reproduce the same bug with Stronghold and Starcraft.

[nigroller (nigroller)]

I mean, It happened when I unplugged the cord during gameplay. Sorry for not being sufficiently specific.

[Andreas Moog (ampelbein)]

Ok so if this is reproducabe:
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.

[nigroller (nigroller)]

Ok, so far I did what you recommended and managed to reproduce the bug, but in a different way. It happens when the power cable is unplugged when my wireless card isn't turned on, when it's on, gnome-power-manager doesn't crash. I'm uploading the backtrace files when the wireless card is either on or off.

[Andreas Moog (ampelbein)]

Thanks for the reproduce steps. Your backtrace is not complete I'm afraid. After gdb emits

"Program received signal SIGSEGV, Segmentation fault."

you typed continue, which is wrong. From there on, please use the commands:

backtrace full
info registers
thread apply all backtrace

and upload again. Thank you for your cooperation.

[nigroller (nigroller)]

Here you go.

[Scott Howard (showard314)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Since your report there has been significant changes and improvements to power management in Ubuntu and gnome-power-manager. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

[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!