Merge lp:~mterry/unity8/fix-greeter-retry into lp:unity8
Status: | Superseded |
---|---|
Proposed branch: | lp:~mterry/unity8/fix-greeter-retry |
Merge into: | lp:unity8 |
Prerequisite: | lp:~ci-train-bot/unity8/unity8-ubuntu-xenial-landing-041 |
Diff against target: |
12 lines (+1/-1) 1 file modified
qml/Greeter/Greeter.qml (+1/-1) |
To merge this branch: | bzr merge lp:~mterry/unity8/fix-greeter-retry |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Unity8 CI Bot | continuous-integration | Needs Fixing | |
Unity Team | Pending | ||
Review via email: mp+289299@code.launchpad.net |
This proposal has been superseded by a proposal from 2016-03-17.
Commit message
Fix showing "Retry" in password prompt when turning on screen in tablet mode.
Description of the change
When told to show the greeter (power button press or dbus request), we forcibly reset greeter state. This lets us catch when passwords change or the like by resetting the PAM stack.
In one case, we weren't resetting state hard enough and the password prompt thought it hadn't been prompted yet by PAM but still wasn't authorized. So it showed a "Retry" button instead of the normal password prompt.
This fixes that by going through the proper channels for a reset.
= To reproduce =
- Use tablet mode
- Log in
- Lock screen
- Turn screen on
- Turn screen off
- Turn screen on
You should now see a "Retry" button in the greeter password field.
= 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:2297 /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/761/ /unity8- jenkins. ubuntu. com/job/ build-0- fetch/1000 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= vivid+overlay/ 1016 /unity8- jenkins. ubuntu. com/job/ build-1- sourcepkg/ release= xenial/ 1016 /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= vivid+overlay/ 1014/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=amd64, release= xenial/ 1014/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= vivid+overlay/ 1014/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=armhf, release= xenial/ 1014/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= vivid+overlay/ 1014/console /unity8- jenkins. ubuntu. com/job/ build-2- binpkg/ arch=i386, release= xenial/ 1014/console
https:/
Executed test runs:
SUCCESS: https:/
SUCCESS: https:/
SUCCESS: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
FAILURE: https:/
Click here to trigger a rebuild: /unity8- jenkins. ubuntu. com/job/ lp-unity8- ci/761/ rebuild
https:/