Thanks to all those who attached logs. All logs show trailing binary 0x02 (CONTROL-B) bytes at the end of the POWER_SUPPLY_MANUFACTURER value. So I think this single rogue byte, encoded in the battery meta- data, is ironically indirectly causing you high battery drain :-(
The fact that we've so far only seen this problem with power supply manufacturer strings suggests that it is *highly* unlikely there will be any adverse effects of the proposed fix since even if an Upstart job were to care about a battery device, it really shouldn't be caring about the specific manufacturer details. Please could those affected by this issue test the fix available in the following PPA: https://launchpad.net/~jamesodhunt/+archive/bug-829980 To install the fix: 1) In a terminal, run: sudo add-apt-repository ppa:jamesodhunt/bug-829980 This will show you some text and ask you to press return to enable this repository. 2) Run: sudo apt-get update && sudo apt-get upgrade Step (2) should pull in the latest test version of Upstart (version "1.3-0ubuntu12~bug829980"). If so, reboot as normal and then update this bug with your results. [Note: I've tested this fix, but note that I do not have access to any of these bad batteries. So, in the unlikely event you *do* experience issues with the fix, remove your battery and boot from AC power]. Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/829980 Title: upstart-udev-bridge eats 100% cpu calling dbus_message_iter_append_basic() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/829980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
