You can reproduce this latest race with the following script: adb reboot && adb wait-for-device && adb shell 'while ! gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method com.canonical.UnityGreeter.HideGreeter 2>/dev/null 1>&2; do echo -n .; done' && echo -e '\nDid it work?'
This exact race does not seem to have occurred in 8.00+14.10.20140930.2-0ubuntu1. But does in 8.00+14.10.20141006-0ubuntu1. I don't think the appearance of this race is due to my previous unlock- device changes, as this script does not exercise the unlock-device command. This is something new that needs investigation. -- 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/1370644 Title: unity8-autopilot device unlock seems racy Status in “unity8” package in Ubuntu: Triaged Bug description: In some test runs, we see unlocking fail with: I: Unlock failed, script output: 'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files It's not reliably reproducible, but probably happens at least once a day for us in CI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1370644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
