Bugzilla – Bug 11534
Re-enter password skips keyboard
Last modified: 2012-02-27 17:19:03 UTC
r4995 Just for grins, I tried connecting to a different wireless network that Fab4 detected. Entered some random WPA password and Fab4 failed to connect. On the 'Can't Connect' screen I chose the option to 'Re-enter password', then 'Enter WPA Password'. But it immediately tries to connect again without giving the opportunity to enter the password. Coming back to the Can't Connect screen, it shows 'You entered:nil'. If I change networks, same thing. No chance to enter a password.
I don't see this. Can qa please reproduce?
Still seeing it with r5000. Haven't been through a virgin setup recently - this is specifically using network setup. A major change to the wireless network setup flow is that if you change networks and the Fab4 has a stored passphrase for the SSID it will always try to connect first, before giving the user an opportunity to (re)enter a passphrase. Prior to this, you were always given the chance to either right-arrow through the stored password, or else enter a new one. I suspect that it has to do with the Fab4 knowing that it has a stored passphrase for the network and some kind of faulty logic that incorrectly using the new setup flow instead of presenting the keyboard like it should.
QA Confirmed. r4875 will prompt for a Password screen, r5007 does not Setup a unit, attach to either Wired or Wireless After Setup... Settings > Advanced > Setup Networking Walk through wireless setup Right after 'choose network' the user should be presented with a Password Screen (r4875 does) instead, r5007 will jump to connecting NOTE: for my units, clicking on the 'reenter password' screen after a failure will cause the unit to crash and reboot
I'm not sure whether this needs to be targeted for MP, as I'm pretty certain that during initial setup you _do_ get the keyboard back when re-entering the password. It's only when changing networks via 'Setup Network' that I'm seeing this.
I can't recreate this with r5062. James can you retest please.
r5058 (latest on SN) appears to be working
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version. If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.