Unfortunately I am not a member of Ubuntu Bug Control and with this I
have no access to
https://bugs.launchpad.net/bugs/929755
which is still private.
There should be a full stacktrace following the dublicate entries you
have brought here.
Can you copie it here?(Or set the report to public?
I have looked through the dublicats and added tags that fits for them.
The crash is not limited to pandaboard.
Insted it occures on different architectures.
I adapt the summary for this.
** Summary changed:
- pandaboard - upowerd crashed with signal 5 in
Hi James,
I have to say sorry.
I do only on bug triaging and not coding(have not done for several years
- you loose what you do not train). So, you do not have to orientate to
me.
When you want to work on fixing this, please fell absolutely free.
greetings
melchiaros
--
You received this
Heh, no apology necessary :) I was just trying to get the information
that you were looking for.
Now that we do have enough information to reproduce and get core dumps
etc, whom do we triage _to_?
--
You received this bug notification because you are a member of Desktop
Packages, which is
Hi melchiaros,
This is likely the same crash as in
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/929755/comments/2
. As far as I can tell, this happens because upower expects some battery
to be there that isn't there. In bug 929755, it's a wiimote, in other
cases, it's a bluetooth mouse.
Okay, I've figured out the sigtrap confusion. Apparently, it's what the
Gnome devs think is a good signal to tie in to g_error() if you have
debugging turned on (we compile glib with debugging turned on?).
I've also managed to find the code that's erroring. Take a look at lines
1706-1711:
In this case please install the needed dbg packages (see stacktrace
attached on this report)manually and wait until the crash occures again.
Following this:
https://wiki.ubuntu.com/DebuggingProgramCrash
you can examine locally and look if the stacktrace is good enough.
If it is please file a
7 matches
Mail list logo
