@jm-leddy o.K,
I have looked a little bit arround. Looking at: https://bugs.launchpad.net/ubuntu/+source/upower/+bugs?orderby=-heat&start=0 upower bugs seems to get not so much attention(to say it nice).There lay 60 open reports arround. Even when you use advance search you see that there where at whole life of launchpad only 94 reports and a closing rate (of whatever reason) of 34 is indeed low. With the dublicates linked here the flame rate has increased to 266, which is the fourth highest one recently there, so there is a chance that this here will get attention. Anyway, I think that involving the original developers of upower makes sense here, because the crash occures in different versions of upower and on different architectures(see the comments above). So there could be interest by them to handle this problem. This brings the next problem with it. There bugtracker at https://bugs.freedesktop.org/ seems to be used only sporadic. Following http://upower.freedesktop.org/ they prefer contacted by mailing list http://lists.freedesktop.org/mailman/listinfo/devkit-devel James, because you have a plan what is going on here, could you contact them on the mailing list as they wish it? When they do not react there I could open a ticket on their bugtracker. -- 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: 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
