[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

** Changed in: oem-priority/xenial
   Status: Fix Committed => Fix Released

-- 
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 Released
Status in OEM Priority Project xenial series:
  Fix Released
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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Launchpad Bug Tracker]

This bug was fixed in the package network-manager-applet -
1.2.6-0ubuntu0.16.04.4

---
network-manager-applet (1.2.6-0ubuntu0.16.04.4) xenial; urgency=medium

  * debian/patches/git_fix_wrong_status_for_wireless_toggle.patch:
* Fix failing to load / use nma gir bindings. LP: #1107935

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 15:04:49
+

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 2.21.63.5

---
ubiquity (2.21.63.5) xenial; urgency=medium

  * Cherry-pick support for WPA2 Enterprise. LP: #1107935
  * Automatic update of included source packages: console-setup
1.108ubuntu15.4.

 -- Dimitri John Ledkov   Tue, 31 Oct 2017 17:45:29
+

** Changed in: ubiquity (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Yuan-Chen Cheng]

** Tags removed: risk
** Tags added: sru

-- 
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

-- 
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Cyrus Lien]

** Changed in: oem-priority/xenial
   Status: Confirmed => Fix Committed

-- 
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:
  Confirmed
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Dimitri John Ledkov]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Cyrus Lien]

Verified image (serial 20171101), the issue was fixed.

The package name and version in the image are:  
network-manager-gnome 1.2.6-0ubuntu0.16.04.4 
ubiquity 2.21.63.5  

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Dimitri John Ledkov]

Desktop images at http://cdimage.ubuntu.com/xenial/daily-live/pending/
contain all the relevant packages and are good to go to be tested.

These images have serial 20171101 or any later.

Please test these images and confirm if the proposed updates resolve
this issue.

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Łukasz Zemczak]

Hello Mathieu, or anyone else affected,

Accepted ubiquity into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubiquity/2.21.63.5
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: ubiquity (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: In Progress => Fix Committed

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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 Committed
Status in ubiquity source package in Xenial:
  Fix Committed

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.

  : "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

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Dimitri John Ledkov]

Test packages for this fix in xenial are now available from this ppa
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3014

It is possible to enable and upgrade packages from this ppa in place,
clear the network manager status (i.e. disconnect network, edit
connections and delete it). Clear ubiquity / oem-config state and rerun
the installer.

I will push these packages to proposed, to get a proposed desktop image
out with these changes in.

Please let me know if any other images are required for this.

** Description changed:

  [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.
  
  : "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.)

** Changed in: network-manager-applet (Ubuntu Xenial)
   Status: New => In Progress

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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:
  In Progress
Status in ubiquity source package in Xenial:
  In Progress

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.

  : "If the selected network does require
  authentication, Network Manager’s standard dialog should open for you
  to enter those authentication details as s

[Desktop-packages] [Bug 1107935] Re: Support for WPA Enterprise wireless networks

[Dimitri John Ledkov]

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Released

-- 
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:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
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:
  New
Status in ubiquity source package in Xenial:
  In Progress

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.

  ---

  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.

  : "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