The proof of concept works well if the device has swip only lock policy.
But if there is a passcode or passphrase then the problem might be more
complicated.
In the UITK test plan executor [1] I use this to unlock the screen, keep it
locked and shiny:
adb -s ${SERIALNUMBER} shell powerd-cli display on |egrep -v "Display State
requested, cookie is|Press ctrl-c to exit|not fully supported." &
adb -s ${SERIALNUMBER} shell powerd-cli active |egrep -v "requested, cookie
is|Press ctrl-c to exit|not fully supported." &
adb -s ${SERIALNUMBER} shell "sudo -u phablet -i gdbus call --session --dest
com.canonical.UnityGreeter \
--object-path / \
--method
com.canonical.UnityGreeter.HideGreeter|grep -v '\(\)'"
adb -s ${SERIALNUMBER} shell "echo 0000|sudo -S dbus-send --system
--print-reply \
--dest=org.freedesktop.Accounts \
/org/freedesktop/Accounts/User32011 \
org.freedesktop.DBus.Properties.Set \
string:com.canonical.unity.AccountsService \
string:demo-edges
variant:boolean:false 2>&1|grep -v password|egrep -v '\(\)|method return'"
It uses '0000' password.
[1] http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-
toolkit/trunk/view/head:/tests/uitk_test_plan.sh
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New => Won't Fix
** Changed in: ubuntu-ui-toolkit
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1228061
Title:
[touch]Provide a sane solution to unlock the screen on touch devices
during autopilot test run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1228061/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
