Fails To Connect To WPA2 WiFi

Bug #1682701 reported by Aere Greenway
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager-applet (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The task-bar applet showing network connection will not connect to the DSL modem wireless, as it used to do in prior releases.

I tried three different wireless dongles, all with the same result.

I'm running the live 17.04 system, and I tried it on three different machines as well.

Other than the machine I submitted the bug report on (which also has ethernet connectivity), all of my other machines depend on wireless, so 17.04 is not usable.

I tried both Lubuntu 17.04 and Xubuntu 17.04, and both live-systems have the same problem.

1) lubuntu@lubuntu:~$ lsb_release -rd
Description: Ubuntu 17.04
Release: 17.04

2) lubuntu@lubuntu:~$ sudo apt-cache policy network-manager-applet
N: Unable to locate package network-manager-applet

3) I expected the wireless to connect, as it has always done in prior releases.

4) It tried connecting for a period of time, then gave up.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager-gnome 1.4.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
CasperVersion: 1.380
CurrentDesktop: LXDE
Date: Fri Apr 14 02:52:32 2017
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.0.1 dev enp3s0 proto static metric 100
 192.168.0.0/24 dev enp3s0 proto kernel scope link src 192.168.0.2 metric 100
LiveMediaBuild: Lubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
NetworkManager.conf:
 [main]
 plugins=ifupdown,keyfile

 [ifupdown]
 managed=false
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH
 Wired connection 1 d5e527dc-f755-3a8e-978a-a4233102a518 802-3-ethernet 1492138159 Fri 14 Apr 2017 02:49:19 AM UTC yes 4294966297 no /org/freedesktop/NetworkManager/Settings/0 yes enp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0
 TEMAIRANET 19205db9-bf9d-4768-9851-5e7a2941266a 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/1 no -- -- --
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 enp3s0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 d5e527dc-f755-3a8e-978a-a4233102a518 /org/freedesktop/NetworkManager/ActiveConnection/0
 wlx0025223f6edb wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.4.4 connected started full enabled enabled enabled enabled enabled

Revision history for this message
Aere Greenway (aere) wrote :
Revision history for this message
Aere Greenway (aere) wrote :

I upgraded a 16.10 system with working wireless, to 17.04, and after reboot, the wireless no longer connects.

The wireless sees the wireless networks available, but it will not connect.

I have a long WPA2 passphrase (22 characters, with upper and lower case letters).

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

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

Changed in network-manager-applet (Ubuntu):
status: New → Confirmed
Revision history for this message
Frank Sokolic (sokolic) wrote :

Have just upgraded from 16.10 to 17.04 and can no longer connect to the router using my D-Link EDUP 802.11N wireless usb adapter. It worked fine with 16.10.

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.