[Bug 1479014] Re: "Cancel" button does not work at first when selecting user that is not listed on login screen

[The Unknown]

Each time I wrote "Bug" in the new description it seems to have linked
to some other irrelevant bug, please ignore those links.

** Description changed:

- I am running Ubuntu Gnome 15.04, and I have recently noticed that when
- logging in (not from suspend), if I click on "Not listed?", it takes me
- to a place where I can enter the username, but if I have navigated to
- this place accidentally, if I press "Cancel" nothing happens, until I
- press "Next", then the little cog appears, and the "Cancel" button
- functions as it should.
+ [Impact]
  
- So I am filing this bug report as I should not need to press "Next", to
- get the cog, and the "Cancel" button functioning normally.
+ There are three patches in this one fix. So there are three bugs which
+ are fixed:
+ 
+ - Bug1: If the "Next" button ever gets set to "Sign In", it won't
+ get reset to next until the next question asked by pam.
+ 
+ - Bug2: 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.
  
  
- ---
+ - Bug3: Users are not allowed to cancel if the verification has not started yet and they are typing in their username.
  
- OS Information:
+ These are rather important things to be fixed as they make the login
+ process more confusing and difficult.
  
-     No LSB modules are available.
-     Distributor ID:	Ubuntu
-     Description:	Ubuntu 15.04
-     Release:	15.04
-     Codename:	vivid
+ How the bugs are fixed:
  
- Package Information:
+ - Bug1 fix: Reset "Next" button to "Next" when asking for username.
  
-     gdm:
-       Installed: 3.14.1-0ubuntu3
-       Candidate: 3.14.1-0ubuntu3
-       Version table:
-      *** 3.14.1-0ubuntu3 0
-             500 http://gb.archive.ubuntu.com/ubuntu/ vivid/universe amd64 Packages
-             100 /var/lib/dpkg/status
+ - Bug2 fix: Disallow the user to press "Next" when the username field is
+ empty up front.
+ 
+ - Bug3 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 Bug1: 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 Bug2:
+ 
+ On the login screen click "Sign In?", then before doing anything else
+ press "Cancel". If nothing happens, you have successfully reproduced
+ this bug.
+ 
+ - Reproduce Bug3:
+ 
+ On the login 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.

** Description changed:

  [Impact]
  
  There are three patches in this one fix. So there are three bugs which
  are fixed:
  
- - Bug1: 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.
  
- - Bug2: 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.
  
- 
- - Bug3: Users are not allowed to cancel if the verification has not started yet and they are typing in their username.
+ - 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:
  
- - Bug1 fix: Reset "Next" button to "Next" when asking for username.
+ - Bug-1 fix: Reset "Next" button to "Next" when asking for username.
  
- - Bug2 fix: Disallow the user to press "Next" when the username field is
- empty up front.
+ - Bug-2 fix: Disallow the user to press "Next" when the username field
+ is empty up front.
  
- - Bug3 fix: authPrompt no longer ignores the request to cancel before a
+ - 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 Bug1: I am terribly sorry but this is a bug is not one that
+ - 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 Bug2:
+ - Reproduce Bug-2:
  
  On the login screen click "Sign In?", then before doing anything else
  press "Cancel". If nothing happens, you have successfully reproduced
  this bug.
  
- - Reproduce Bug3:
+ - Reproduce Bug-3:
  
  On the login 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.

** 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
+ - 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-2:
+ - Reproduce Bug 2:
  
  On the login 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
  entering your username (or any text), then instead of pressing "Next",
  press "Cancel", if nothing happens then you have successfully reproduced
  the bug.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1479014

Title:
  "Cancel" button does not work at first when selecting user that is not
  listed on login screen

Status in Ubuntu GNOME:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Vivid:
  Triaged

Bug description:
  [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
  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.

  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.

  [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 2:

  On the login 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 login 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1479014/+subscriptions