Automated screen unlock not working on wily images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Test Cases |
Invalid
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu) |
Invalid
|
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
Changed in unity8 (Ubuntu): | |
importance: | Undecided → High |
Changed in unity8 (Ubuntu): | |
assignee: | nobody → Josh Arenson (josharenson) |
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.