Ubiquity no longer prompts to join available WiFi networks

Bug #1572793 reported by Martin Wimpress 
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
High
Mathieu Trudel-Lapierre
Xenial
Fix Released
High
Mathieu Trudel-Lapierre

Bug Description

[Impact]
Any user doing an install on a system with a wireless device.

[Test cases]
Install Ubuntu on a system with a wireless device. Verify that you are presented with a wizard panel asking you which network in range you would like to connect to.

[Regression Potential]
None. This corrects an issue specific to building NM 1.2 which has been ported to GDBus. Reverting to a previous version of NM should still work with the new property name, which is the correct name as Documented and as exported by the API.

---

While testing the Ubuntu and Ubuntu MATE 16.04 20160420.1 images Ubiquity is no longer prompting to join available WiFi networks.

`nmcli dev` is correctly reporting wireless and wired devices. It is possible to use the network indicator in Ubiquity to manually join a wireless network. This issue also affects oem-config both during the initial install and after preparation for the customer.

Related branches

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubiquity (Ubuntu):
status: New → Confirmed
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1572793

tags: added: iso-testing
Revision history for this message
Gianfranco Costamagna (costamagnagianfranco) wrote :

Hi Martin, I can't answer on irc, but I read it (irclogs.ubuntu FTW).

What is exactly the issue? I see "video screwed up", I see no applet, but I don't understand how can it be a virtualbox fault.

For the video you can try:
dpkg-reconfigure virtualbox-guest-dkms, and remove (optionally) the xserver-xorg-legacy package (useless with 5.0.18 driver).

the problem might be that you are hitting LP: #1571156 bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

What do you mean "prompting"? Do you have the nm-applet and can use it to connect?

description: updated
Changed in ubiquity (Ubuntu):
status: Confirmed → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Changed in ubiquity (Ubuntu Xenial):
status: New → In Progress
importance: Undecided → High
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Martin, 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.1 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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
Changed in ubiquity (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 16.10.1

---------------
ubiquity (16.10.1) yakkety; urgency=medium

  [ Iain Lane ]
  * misc.py: Ask for the 'State' property instead of 'state'. Fixes display
    of wireless page. (LP: #1572793)

  [ Mathieu Trudel-Lapierre ]
  * Abitrary version number change.
  * Move sources to yakkety.
  * Automatic update of included source packages: choose-mirror
    2.65ubuntu7, console-setup 1.142ubuntu1, preseed 1.71ubuntu2.

 -- Mathieu Trudel-Lapierre <email address hidden> Fri, 29 Apr 2016 16:28:50 -0400

Changed in ubiquity (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

Confirmed this fix in the proposed packaged, everything seems shiny.

I confirmed that after an OEM install, enabling proposed, updating, and finally clicking "Prepare for shipping to user", Ubiquity behaves as expected during the first-run user config:

1) When not connected to Ethernet and you have WiFi hardware available, Ubiquity again prompts you to join a WiFi network, and if you do, ubi-timezone will correctly guess your timezone

2) When connected to Ethernet, Ubiquity will not prompt you to join a WiFi network, and ubi-timezone will use the Ethernet connection to guess your timezone

3) When not connected to Ethernet and you decline to join a WiFi network, Ubiquity still works as expected (but ubi-timezone understandably can't guess your timezone)

Only thing I can't test is a fresh install as that can't really be done properly without a remastered ISO. But as this fix really matters for OEM installs and eventually for the 16.04.1 ISOs, I feel it's safe to mark this as "verification-done".

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 2.21.63.1

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

  [ Iain Lane ]
  * misc.py: Ask for the 'State' property instead of 'state'. Fixes display
    of wireless page. (LP: #1572793)

 -- Mathieu Trudel-Lapierre <email address hidden> Fri, 29 Apr 2016 13:40:33 -0400

Changed in ubiquity (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote : Update Released

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.