I just confirmed that this is a regression is caused by the final deprecation of dbus-glib in NM 1.2x, and it's replacement by gdbus. As part of this work, the code which requests secrets from a secret-agent, now uses code generated from the introspection XML to make the actual DBus method call. As this generated function doesn't have a parameter to allow the client to specify a timeout, the default ( ~25s ) gets used. This contrasts to the old code which explicitly specified a 120s timeout as a parameter to dbus_g_proxy_begin_call_with_timeout().
So, if the user types the passphrase ( or 64-char hex key ) in < ~25s, the connection should work. The maximum length passphrase ( repeating blocks of '1234567890' ) is ~40 characters before the timeout makes it impossible to type anything longer. An upstream bug had been reported and is currently in-progress: https://bugzilla.gnome.org/show_bug.cgi?id=767321 Currently the only workaround for this is to manually update the system connection file for the AP with the psk and restart the device. It then should be possible to tap the access point in the WiFi list, and as long as the passphrase is correct in the connection file, NM should reconnect to the network automatically when available. You can accomplish this by stopping NM on the device and editing the connection file directly, or copying the connection file from the device, editing, and pushing it back ( via adb ). System connection files are found in the directory /etc/NetworkManager/system-connections. I've verified with a krillin running OTA11 that passphrases up to 63 characters work correctly once they've been pre-populated in a connection file. I haven't yet verified a 64-character hex key, but will make sure this is tested as well before we release the final fix. ** Bug watch added: GNOME Bug Tracker #767321 https://bugzilla.gnome.org/show_bug.cgi?id=767321 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1593686 Title: Wi-Fi passphrase limit introduced in OTA-11 Status in Canonical System Image: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: After installing OTA-11, connectivity to a Cisco AP1131AG AP (IOS 12.4-25d.JA2) stopped working, possibly due to the length of the WPA pass-phrase, which was 29 characters long. The pass-phrase requirement is from 8 to 63 characters. After reducing the pass- phrase to 14 (and sometimes 15) characters connectivity is restored. Attempting to connect to a Cisco 1702i (IOS 15.3-3.JC1) which has both 802.11 ac (wave 1) and 802.11n radios has similar problems: (a) it cannot "see" the 802.11ac radio at all (interface Dot11Radio0) and although it "sees" the 802.11n radio (interface Dot11Radio1) it cannot connect. The pass-phrase length requirement on both radios is 18 to 128 characters. In both cases the Cisco APs do not log any event. Prior to OTA 11 connectivity worked normally on OTA 10.1 OS: Ubuntu 15.04 (OTA-11) on BQ Aquaris E5 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1593686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
