The verification of the Stable Release Update for ubiquity has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1107935 Title: Support for WPA Enterprise wireless networks Status in OEM Priority Project: Fix Committed Status in OEM Priority Project xenial series: Fix Committed Status in network-manager-applet package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in network-manager-applet source package in Xenial: Fix Released Status in ubiquity source package in Xenial: Fix Released Bug description: [Impact] In some installations, WPA2 Enterprise support is required to have access to the network to complete the installation. [Test cases] 1) Start installer from ubuntu-desktop image. 2) Follow the prompts to connect to the wireless network 3) Validate that a new dialog appears asking for the network password or credentials. [Regression potential] This impacts all wireless connections and so the type of regression to look for in general failure to connect to a secured wireless network when the authentication settings are correct (pre-shared key is correct), or in cases of connecting to an unsecured network. For network-manager-applet: - ubiquity uses nma gir to implement above - the nma gir is missbuilt in xenial, and does not have correct dependencies, thus is not usable in the same process when both NM and NMA are in use. This was fixed in zesty. I have cherrypicked a fix for misscompiled gir. There is minimal regression potential (just a rebuild) because there are no reverse dependencies of the nma gir in xenial. And there are unlikely to be any external users of nma gir on xenial, since it is broken / has wrong dependencies. --- Ubiquity doesn't appear to support WPA-Enterprise wifi networks -- there's just a single textbox shown to enter a passphrase, but most WPA-Enterprise will require at least a specific username and password, and possibly certificates. NM should already export this information on DBus, it should be a matter of using libnm-gtk to query the user for the connection information rather than prompting for it directly from the installer. <http://goo.gl/2iqv6j>: "If the selected network does require authentication, Network Manager’s standard dialog should open for you to enter those authentication details as soon as you choose “Connect…”." (Not to be confused with bug 1018160, about WEP networks.) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1107935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
