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.
I can reproduce it pretty frequently, let me know if you need more info.
One thing I can't figure out is why it raises signal 5 (SIGTRAP). I
thought that was only for gdb?
** Changed in: upower (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112907
Title:
pandaboard - upowerd crashed with signal 5 in
dbus_g_connection_register_g_object()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
