Wireless screen doesn't connect to selected wireless network

Bug #1164567 reported by Jeremy Bícha
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Medium
Unassigned
ubiquity (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

This is with the Ubuntu GNOME Beta 2 candidate image.

1. Select Try Ubuntu GNOME
2. Don't connect to wifi.
3. Find Install Ubuntu-GNOME in the Activities Overview and start the installation.
4. When you get to the Wireless screen, select a wifi network (In my case, the wifi network is an open network but captive portal)
5. Click Connect.
6. ...Nothing happens

Workaround:
Click the network menu in the top right corner and connect to the wifi point instead.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.1
ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5
Uname: Linux 3.8.0-16-generic i686
ApportVersion: 2.9.2-0ubuntu5
Architecture: i386
CasperVersion: 1.330
Date: Thu Apr 4 15:20:26 2013
InstallCmdLine: file=/cdrom/preseed/ubuntu-gnome.seed boot=casper initrd=/casper/initrd.lz quiet splash --
LiveMediaBuild: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha i386 (20130402.1)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Jeremy Bícha (jbicha) wrote :
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/1164567

tags: added: iso-testing
Revision history for this message
Brian Murray (brian-murray) wrote :

This might be an issue with network-manager.

tags: added: ubi-wireless
Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Are you sure the network is open? Seems to me like it's failing to auth due to cached auth data:
#define WLAN_REASON_PREV_AUTH_NOT_VALID 2

Apr 4 15:19:15 ubuntu-gnome NetworkManager[1958]: <info> (wlan0): supplicant interface state: completed -> authenticating
Apr 4 15:19:15 ubuntu-gnome kernel: [ 131.450269] wlan0: direct probe to 10:8c:cf:b0:0a:38 (try 1/3)
Apr 4 15:19:15 ubuntu-gnome kernel: [ 131.653202] wlan0: direct probe to 10:8c:cf:b0:0a:38 (try 2/3)
Apr 4 15:19:15 ubuntu-gnome kernel: [ 131.857096] wlan0: direct probe to 10:8c:cf:b0:0a:38 (try 3/3)
Apr 4 15:19:15 ubuntu-gnome kernel: [ 132.061008] wlan0: authentication with 10:8c:cf:b0:0a:38 timed out
Apr 4 15:19:15 ubuntu-gnome NetworkManager[1958]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Apr 4 15:19:15 ubuntu-gnome NetworkManager[1958]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 4 15:19:16 ubuntu-gnome wpa_supplicant[2822]: wlan0: SME: Trying to authenticate with 10:8c:cf:b0:0a:37 (SSID='IT-ology-Events' freq=5805 MHz)
Apr 4 15:19:16 ubuntu-gnome kernel: [ 132.334798] wlan0: deauthenticating from 8c:b6:4f:c9:a7:c7 by local choice (reason=2)
Apr 4 15:19:16 ubuntu-gnome kernel: [ 132.337091] wlan0: authenticate with 10:8c:cf:b0:0a:37
Apr 4 15:19:16 ubuntu-gnome kernel: [ 132.382996] wlan0: send auth to 10:8c:cf:b0:0a:37 (try 1/3)
Apr 4 15:19:16 ubuntu-gnome NetworkManager[1958]: <info> (wlan0): supplicant interface state: scanning -> authenticating

That said, it seems like there are further issues with connecting; direct probes fail which may indicate bad signal.

Additionally, you may want to try disabling 11n; which may help:

sudo rmmod iwlwifi
sudo modprobe iwlwifi 11n_disable=1

Or try to change regulatory domain:

sudo iw reg set US

And try to connect again, see if either changes improves the situation.

Thanks!

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Dimitri John Ledkov (xnox) wrote :

we do download and verify checksum of http://start.ubuntu.com/connectivity-check.html which should timeout/return eventually with a broken connection / captive portal.

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
Jeremy Bícha (jbicha) wrote :

I was not able to duplicate this bug with yesterday's Ubuntu GNOME 13.04 image. I successfully connected to the same captive portal from earlier this month from the wireless screen in ubiquity.

Changed in network-manager (Ubuntu):
status: Incomplete → Invalid
Changed in ubiquity (Ubuntu):
status: Confirmed → Invalid
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.