@Tim, Ok, I am not sure how to make it shorter, I have done my best to write it in the best way I can, if you can think of a better way of putting it all then please do, but I have done my best. I missed the regression potential section because I am not sure what potential regressions exist, so I wouldn't know what to put in that section because I do not know of any, if you could give me some better advice for what to put in that section then please do.
** Description changed: [Impact] There are three patches in this one fix. So there are three bugs which are fixed: - - Bug 1: If the "Next" button ever gets set to "Sign In", it won't + - 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 + - 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 + - Bug [3]: Users are not allowed to cancel if the verification has not started yet and they are typing in their username. 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 [1] fix: Reset "Next" button to "Next" when asking for username. - - Bug 2 fix: Disallow the user to press "Next" when the username field + - 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 [3] fix: authPrompt no longer ignores the request to cancel before + a user has started verification and is still typing in their username. [Test Case] - - Reproduce Bug-1: I am terribly sorry but this is a bug is not one that - I have been experiencing, even though I was asked to include the patch - for this one. So I cannot write detailed instructions on how to - reproduce it, because I'm not so clear on how to reproduce it myself. So - somebody else will have to fill out this section. + - Reproduce Bug [1]: - - Reproduce Bug 2: + 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. - On the login screen click "Sign In?", then before doing anything else + - 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: + - Reproduce Bug [3]: - On the login screen click "Sign In", then in the username field, start + 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 - the bug. + this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1479014 Title: "Cancel" button does not work at first when selecting user that is not listed on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1479014/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
