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
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
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
--
gnome-power-manager crashed with SIGSEGV in start_thread()
https://bugs.launchpad.net/bugs/360278
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Here you go.
** Attachment added: gdb-gnome-power-manager.txt
http://launchpadlibrarian.net/25867468/gdb-gnome-power-manager.txt
--
gnome-power-manager crashed with SIGSEGV in start_thread()
https://bugs.launchpad.net/bugs/360278
You received this bug notification because you are a member of
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
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 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.
**
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.
--
gnome-power-manager crashed with SIGSEGV in
I mean, It happened when I unplugged the cord during gameplay. Sorry for
not being sufficiently specific.
--
gnome-power-manager crashed with SIGSEGV in start_thread()
https://bugs.launchpad.net/bugs/360278
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
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.
--
gnome-power-manager crashed with
10 matches
Mail list logo
