Public bug reported: The method to automatically unlock the screen prior to running autopilot tests is not working on wily images. For example:
https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily- mako/417/console The CI automation uses this script to setup and perform the unlock: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh The failure is seen on images from "ubuntu-touch/devel-proposed/ubuntu", in this case image 276. Attached is the full console log from that run. [The relavent messages are:] I: Unlock attempt 1 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 2 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 3 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 4 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 5 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Too many unlock failures, giving up ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1498541 Title: Automated screen unlock not working on wily images Status in unity8 package in Ubuntu: New Bug description: The method to automatically unlock the screen prior to running autopilot tests is not working on wily images. For example: https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-wily- mako/417/console The CI automation uses this script to setup and perform the unlock: http://bazaar.launchpad.net/~ubuntu-test-case-dev/ubuntu-test-cases/touch/view/head:/utils/host/reboot-and-unlock.sh The failure is seen on images from "ubuntu-touch/devel- proposed/ubuntu", in this case image 276. Attached is the full console log from that run. [The relavent messages are:] I: Unlock attempt 1 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 2 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 3 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 4 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Unlock attempt 5 failed, script output: 'initctl: unable to determine sessions initctl: unable to determine sessions Error connecting: Cannot autolaunch D-Bus without X11 $DISPLAY ' I: Too many unlock failures, giving up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1498541/+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
