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: http://maemo.org/api_refs/4.0/dbus-glib/dbus-gobject_8c-source.html http://comments.gmane.org/gmane.comp.gnome.apps.gnucash.user/23290 -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
