otto runner has locked unity7 session from time to time

<vila> Saviq: ha ! slow network then, worked on
<Saviq> vila, just wanted to say that maybe network is slow
<Saviq> vila, still, we should disable screen lock completely on otto, shouldn't we ;)
<vila> Saviq: oh yes
<Saviq> or at least inhibit it during test runs
<vila> Saviq: there is no screen to save there !
<Saviq> vila, I imagined so
<vila> Saviq: so when it happens it's for all tests but it doesn't happen for all jobs ?
<Saviq> vila, yes, when it happens it's 100% failure
<vila> Saviq: thanks
<Saviq> vila, and it happens most often on unity8, gallery - the biggest dependencies probably

Given the irc discussion above I think we should first fix the network issue in the ci lab.
It would be nice to disable the screen saver from otto too but that's more a nice to have than a bug, it would make the otto runner more robust though.

Hmm. otto already disables the screen saver with:

  gsettings set org.gnome.desktop.screensaver idle-activation-enabled false

in run-autopilot.sh.

But this seems to happen too late in this case, the screen locks itself before that script is started.

The impact of this was reduced by faster networking, but the issue still needs to be resolved.