I did a factory reset to resove this issue. That worked. I'll report back if I manage to reproduce, but I'm not shooting for that right now. As noone else is affected, that's not so productive, and I actually prefer an autolocking phone.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1471597 Title: MX4 ubuntu version screen won't auto-lock Status in powerd package in Ubuntu: New Bug description: I'm running 15.04 r2. Initially, the screen locked nicely, but I turned that off for a while (for USB access etc). Now it's turned back on again, and it seems not to lock automatically anymore. Due to battery consumption this is a pretty annoying bug. I ran powerd-cli test: all passed except the first: Test: checkForDbusName(test_dbusname, 0, requests, TRUE) result: FAILED Attached is the full output and the syslog entries for a period where I turn on the screen, wait for 2 minutes, and turn it off again. (lock time is 1 minute. Also doesn't turn off after 1hr) What does it mean that testdbus_name is failing? What should happen when screen autolocks? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1471597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
