Merge lp:~mterry/unity8/no-lock-during-demo into lp:unity8
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Albert Astals Cid | ||||
Approved revision: | 1070 | ||||
Merged at revision: | 1117 | ||||
Proposed branch: | lp:~mterry/unity8/no-lock-during-demo | ||||
Merge into: | lp:unity8 | ||||
Diff against target: |
11 lines (+1/-1) 1 file modified
qml/Shell.qml (+1/-1) |
||||
To merge this branch: | bzr merge lp:~mterry/unity8/no-lock-during-demo | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Albert Astals Cid (community) | Approve | ||
PS Jenkins bot (community) | continuous-integration | Needs Fixing | |
Review via email: mp+227968@code.launchpad.net |
Commit message
When the edge demo is running, don't show the greeter if the screen is turned off. This avoids an odd interaction where parts of the greeter are disabled but the edge demo isn't visible until you slide the greeter away.
Description of the change
In current unity8, when the edge demo is active (past the first screen), the user can turn off the screen, turn it back on, and then see the greeter screen. But parts of it won't be active (like the indicators or the launcher, depending on which part of the edge demo is running). When they slide across the greeter, they'll get back to the demo.
As noted in bug 1283425, this can be a little unexpected. Either we should restart the edge demo or do something that isn't confusing.
I've opted for just not locking the screen when it turns off. This isn't a security flaw since the user hasn't had a chance to set a password. And it would fit with the rest of the edge demo's disabling of features until the user has had a chance to finish it.
Remember that you can re-enable the demo with:
phablet-config edges-intro --enable
== Checklist ==
* Are there any related MPs required for this MP to build/function as expected? Please list.
- No
* Did you perform an exploratory manual test run of your code change and any related functionality?
- Yes
* Did you make sure that your branch does not contain spurious tags?
- Yes
* If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
- NA
* If you changed the UI, has there been a design review?
- NA
FAILED: Continuous integration, rev:1068 jenkins. qa.ubuntu. com/job/ unity8- ci/3562/ jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- utopic- touch/2396 jenkins. qa.ubuntu. com/job/ unity-phablet- qmluitests- utopic/ 564 jenkins. qa.ubuntu. com/job/ unity8- utopic- amd64-ci/ 656 jenkins. qa.ubuntu. com/job/ unity8- utopic- armhf-ci/ 656 jenkins. qa.ubuntu. com/job/ unity8- utopic- armhf-ci/ 656/artifact/ work/output/ *zip*/output. zip jenkins. qa.ubuntu. com/job/ unity8- utopic- i386-ci/ 656 jenkins. qa.ubuntu. com/job/ generic- deb-autopilot- runner- mako/2566 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- armhf/3622 jenkins. qa.ubuntu. com/job/ generic- mediumtests- builder- utopic- armhf/3622/ artifact/ work/output/ *zip*/output. zip s-jenkins. ubuntu- ci:8080/ job/touch- flash-device/ 10304
http://
Executed test runs:
UNSTABLE: http://
UNSTABLE: http://
SUCCESS: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
UNSTABLE: http://
SUCCESS: http://
deb: http://
SUCCESS: http://
Click here to trigger a rebuild: s-jenkins. ubuntu- ci:8080/ job/unity8- ci/3562/ rebuild
http://