Automated screen unlock not working on wily images
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Ubuntu Test Cases |
Undecided
|
Unassigned | ||
| | unity8 (Ubuntu) |
High
|
Unassigned | ||
Bug Description
The method to automatically unlock the screen prior to running autopilot tests is not working on wily images. For example:
https:/
The CI automation uses this script to setup and perform the unlock:
http://
The failure is seen on images from "ubuntu-
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
| Francis Ginther (fginther) wrote : | #1 |
| Changed in unity8 (Ubuntu): | |
| importance: | Undecided → High |
| Michał Sawicz (saviq) wrote : | #2 |
| Changed in unity8 (Ubuntu): | |
| assignee: | nobody → Josh Arenson (josharenson) |
| Michał Sawicz (saviq) wrote : | #3 |
I just tried following http://
$> IMAGE_OPT=
FLASHING DEVICE
Attempting adb reboot bootloader
=========== Device in fastboot ==========
WARNING --developer-mode and --password are dangerous as they remove security features from your device
2015/09/22 19:00:23 Expecting the device to be in the bootloader... waiting
2015/09/22 19:00:23 Device is |mako|
2015/09/22 19:00:23 Flashing version 311 from ubuntu-
6.29 MB / 6.29 MB [======
52.43 MB / 52.43 MB [======
302.71 MB / 302.71 MB [======
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Start pushing /home/michal/
2015/09/22 19:00:59 Done pushing /home/michal/
2015/09/22 19:00:59 Done pushing /home/michal/
2015/09/22 19:00:59 Done pushing /home/michal/
2015/09/22 19:01:02 Done pushing /home/michal/
2015/09/22 19:01:13 Done pushing /home/michal/
2015/09/22 19:01:59 Done pushing /home/michal/
2015/09/22 19:01:59 Created ubuntu_command: /home/michal/
| Changed in unity8 (Ubuntu): | |
| status: | New → Incomplete |
| assignee: | Josh Arenson (josharenson) → nobody |
| Michał Sawicz (saviq) wrote : | #4 |
I just noticed:
+ export REVISION=
[...]
2015/09/22 12:38:36 Flashing version 276 from ubuntu-
The job seems hardcoded on image 276 for some reason, when we're at 311 already, and that's what I've tested. Trying with image 276 now.
| Francis Ginther (fginther) wrote : | #5 |
The jenkins job was indeed hardcoded to use image 276 due to an unbootable image at 277. We then failed to remove this once the image was fixed. Image 311 is working and unlock is successful:
https:/
[log snippet]
INFO:reboot-
I: Unlock attempt 1 failed, script output: 'Error: GDBus.Error:
'
I: Unlock passed
This is now working (transient failed attempts are expected). I think we can close this.
| Changed in unity8 (Ubuntu): | |
| status: | Incomplete → Invalid |
| Changed in ubuntu-test-cases: | |
| status: | New → Invalid |


The above log suggests it's not the tool that's failing, but rather the shell environment isn't complete - i.e. dbus and upstart details are not available.