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 Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1112907 Title: pandaboard - upowerd crashed with signal 5 in dbus_g_connection_register_g_object() Status in “upower” package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: upower 0.9.19-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-216.23-omap4 3.5.7.1 Uname: Linux 3.5.0-216-omap4 armv7l ApportVersion: 2.8-0ubuntu3 Architecture: armhf Date: Fri Feb 1 22:25:19 2013 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2013-01-17 (15 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha armhf+omap4 (20130116) MarkForUpload: True ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: Signal: 5 SourcePackage: upower StacktraceTop: dbus_g_connection_register_g_object () from /usr/lib/arm-linux-gnueabihf/libdbus-glib-1.so.2 ?? () ?? () Title: upowerd crashed with signal 5 in dbus_g_connection_register_g_object() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1112907/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp