"Cancel", "Next", and "Sign In" functioning incorrectly on login or locked screen in "Sign In?" section
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu GNOME |
Fix Released
|
Low
|
Unassigned | ||
gnome-shell (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Vivid |
Won't Fix
|
Low
|
Unassigned | ||
Wily |
Fix Released
|
Low
|
Unassigned |
Bug Description
[Impact]
There are five patches in this one fix. So there are five bugs which are fixed:
- Bug [1]: If the "Next" button ever gets set to "Sign In", it won't
get reset to next until the next question asked by pam.
- Bug [2]: Normally the user isn't allowed to proceed passed
the username question until they've filled it in.
To ensure this, the authprompt code desensitizes
the next button when the number of characters change to
zero.
Unfortunately it fails to desensitize the next button
up front when the entry starts out empty.
- Bug [3]: Users are not allowed to cancel if the verification has not started yet and they are typing in their username.
- Bug [4]: If the authPrompt gets reset for some other reason in the interim, this would mean that we don't fade the authentication prompt back in when it is needed.
- Bug [5]: The user session will crash when the login screen is reactivated due to the fact that the previous the user verifier has not been cleared.
- Bug [6]: (LP: #752220) We currently only cancel the user verifier on reset if verifying, but that means we don't properly cancel it when asking for a username at the "Not Listed" screen.
These are rather important things to be fixed as they make the login process more confusing and difficult.
How the bugs are fixed:
- Bug [1] fix: Reset "Next" button to "Next" when asking for username.
- Bug [2] fix: Disallow the user to press "Next" when the username field is empty up front.
- Bug [3] fix: authPrompt no longer ignores the request to cancel before a user has started verification and is still typing in their username.
- Bug [4] fix: loginDialog now only skips the fade-in if we have already faded-in. It now also only skips resetting if we have already reset.
- Bug [5] fix: We now make sure that once the user verifier has completed its job (of user verification) that it gets cleared so that it does not get in the way later.
- Bug [6] fix: We now unconditionally cancel if the user verifier has been reset.
[Test Case]
- Reproduce Bug [1]:
On the first login screen (or log out - not lock), click "Sign In?", then before doing anything else click "Sign In", if the button allows you to press it and is not greyed out, then you have successfully reproduced this bug.
- Reproduce Bug [2]:
On the locked screen click "Sign In?", then before doing anything else press "Cancel". If nothing happens, you have successfully reproduced this bug.
- Reproduce Bug [3]:
On the locked screen click "Sign In?", then in the username field, start entering your username (or any text), then instead of pressing "Next", press "Cancel", if nothing happens then you have successfully reproduced this bug.
- Reproduce Bug [4]:
Go to the login screen (or locked screen), reset the authentication prompt before you have reached "VERIFICATION_
- Reproduce Bug [5]:
After you have logged in, go back to the login screen, if the user session crashes, then you have successfully reproduced this bug.
- Reproduce Bug [6]:
On the login screen go to the "Not Listed" section, and then attempt to cancel. If it does not let you, then you have successfully reproduced this bug.
[Regression Potential]
As these patches have already been put to practical use in the upstream version, and the patches which have been put to use in this version, have originated from those patches, I would say that the risk of regression is minimal.
tags: | added: gnome3 |
Changed in ubuntu-gnome: | |
milestone: | none → wily |
description: | updated |
description: | updated |
description: | updated |
summary: |
- "Cancel" button does not work at first when selecting user that is not - listed on login screen + "Cancel", "Next", and "Sign In" functioning incorrectly on login or + locked screen in "Sign In?" section |
description: | updated |
description: | updated |
Changed in ubuntu-gnome: | |
status: | Triaged → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https:/ /wiki.ubuntu. com/Bugs/ Upstream/ GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.
Re-assigning to gnome-shell since that draws the UI, still broken as of gnome-shell 3.17.4