OK... I noticed that "initctl emit xsession-init" was always a process on my phone. Even though it wasn't always at 100%.
So I uploaded https://launchpad.net/ubuntu/+source/upstart/1.13.2-0ubuntu15 to wily, which makes it a short-lived task instead of a long-running process. That *probably* works around this bug, although it doesn't really explain the underlying oddity of the 100% cpu. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1494479 Title: initctl stuck taking 100% CPU on "emit xsession" Status in Canonical System Image: New Status in upstart package in Ubuntu: New Bug description: I noticed a battery drain on my mako OTA6 recently. Looking at the Terminal app, initctl was taking 100% CPU. It wasn't slowing down my general experience like bug 1480877 does, because dbus wasn't affected. It was just draining the battery. The specific initctl line was: initctl emit xsession SESSION=ubuntu-touch SESSIONTYPE= It never seemed to die. Had been running for 669 minutes already. Can't find the logs for initctl (where does it put it's output?). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
