Wifi not connecting in Ubuntu 17.04 Beta

**samuelkenno** · February 27th, 2017

Hello.

I ran the Ubuntu 17.04 from USB stick. in order to test it.

Wifi works normally out of the box in Kubuntu 16.04 and 16.10 but not in 17.04.

However I am unable to connect to any wifi network. I'm able to scan the wifi networks around but it happens an error when I try to connect.

I tested also in Kubuntu 17.04 same problem. I already collected some information that could be useful.

I think this might be important to fix before release once this might affect other ubuntu users.

Already tried to google for some solutions but looks like a new problem.

Code:

Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4743] Config: added 'ssid' value 'Valim'
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4746] Config: added 'scan_ssid' value '1'
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4749] Config: added 'key_mgmt' value 'WPA-PSK'
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4751] Config: added 'auth_alg' value 'OPEN'
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4753] Config: added 'psk' value '<omitted>'
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.4765] sup-iface[0x560c6965ec30,wlx48ee0cd9b398]: config: set interface ap_scan to 1
Feb 27 22:21:23 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: SME: Trying to authenticate with 18:62:2c:ca:90:8c (SSID='Valim' freq=2432 MHz)
Feb 27 22:21:23 ubuntu-budgie kernel: [  242.954905] wlx48ee0cd9b398: authenticate with 18:62:2c:ca:90:8c
Feb 27 22:21:23 ubuntu-budgie NetworkManager[1845]: <info>  [1488234083.5114] device (wlx48ee0cd9b398): supplicant interface state: inactive -> authenticating
Feb 27 22:21:23 ubuntu-budgie kernel: [  242.979527] wlx48ee0cd9b398: send auth to 18:62:2c:ca:90:8c (try 1/3)
Feb 27 22:21:23 ubuntu-budgie kernel: [  242.981346] wlx48ee0cd9b398: authenticated
Feb 27 22:21:28 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: SME: Deauth request to the driver failed
Feb 27 22:21:28 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Valim" auth_failures=1 duration=10 reason=CONN_FAILED
Feb 27 22:21:28 ubuntu-budgie NetworkManager[1845]: <info>  [1488234088.5225] device (wlx48ee0cd9b398): supplicant interface state: authenticating -> disconnected
Feb 27 22:21:38 ubuntu-budgie NetworkManager[1845]: <info>  [1488234098.5279] device (wlx48ee0cd9b398): supplicant interface state: disconnected -> scanning
Feb 27 22:21:39 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: CTRL-EVENT-SSID-REENABLED id=0 ssid="Valim"
Feb 27 22:21:39 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: SME: Trying to authenticate with 18:62:2c:ca:90:8c (SSID='Valim' freq=2432 MHz)
Feb 27 22:21:39 ubuntu-budgie kernel: [  259.320219] wlx48ee0cd9b398: authenticate with 18:62:2c:ca:90:8c
Feb 27 22:21:39 ubuntu-budgie NetworkManager[1845]: <info>  [1488234099.9080] device (wlx48ee0cd9b398): supplicant interface state: scanning -> authenticating
Feb 27 22:21:39 ubuntu-budgie kernel: [  259.376041] wlx48ee0cd9b398: send auth to 18:62:2c:ca:90:8c (try 1/3)
Feb 27 22:21:39 ubuntu-budgie kernel: [  259.377651] wlx48ee0cd9b398: authenticated
Feb 27 22:21:44 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: SME: Deauth request to the driver failed
Feb 27 22:21:44 ubuntu-budgie wpa_supplicant[2260]: wlx48ee0cd9b398: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Valim" auth_failures=2 duration=20 reason=CONN_FAILED
Feb 27 22:21:44 ubuntu-budgie NetworkManager[1845]: <info>  [1488234104.9171] device (wlx48ee0cd9b398): supplicant interface state: authenticating -> disconnected
Feb 27 22:21:48 ubuntu-budgie NetworkManager[1845]: <warn>  [1488234108.7306] device (wlx48ee0cd9b398): Activation: (wifi) association took too long, failing activation
Feb 27 22:21:48 ubuntu-budgie NetworkManager[1845]: <info>  [1488234108.7307] device (wlx48ee0cd9b398): state change: config -> failed (reason 'ssid-not-found') [50 120 53]
Feb 27 22:21:48 ubuntu-budgie NetworkManager[1845]: <info>  [1488234108.7312] manager: NetworkManager state is now DISCONNECTED
Feb 27 22:21:48 ubuntu-budgie NetworkManager[1845]: <warn>  [1488234108.7328] device (wlx48ee0cd9b398): Activation: failed for connection 'Valim'
Feb 27 22:21:48 ubuntu-budgie NetworkManager[1845]: <info>  [1488234108.7346] device (wlx48ee0cd9b398): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 27 22:21:48 ubuntu-budgie kernel: [  268.204887] IPv6: ADDRCONF(NETDEV_UP): wlx48ee0cd9b398: link is not ready
Feb 27 22:21:49 ubuntu-budgie NetworkManager[1845]: <info>  [1488234109.3045] device (wlx48ee0cd9b398): set-hw-addr: set MAC address to 9E:60:F8:99:EF:36 (scanning)
Feb 27 22:21:49 ubuntu-budgie kernel: [  269.038123] IPv6: ADDRCONF(NETDEV_UP): wlx48ee0cd9b398: link is not ready
Feb 27 22:21:50 ubuntu-budgie NetworkManager[1845]: <info>  [1488234110.9051] device (wlx48ee0cd9b398): supplicant interface state: disconnected -> inactive

Code:

root@ubuntu-budgie:~# lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 011 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 010 Device 002: ID 3538:0059 Power Quotient International Co., Ltd 
Bus 010 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 2001:3c22 D-Link Corp. 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 04b3:310c IBM Corp. Wheel Mouse
Bus 005 Device 002: ID 258a:0001  
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@ubuntu-budgie:~# ifconfig
enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether fc:aa:14:71:67:27  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)ls
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43  bytes 6028 (6.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 327  bytes 24241 (24.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 327  bytes 24241 (24.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


wlx48ee0cd9b398: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 9e:60:f8:99:ef:36  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Code:

root@ubuntu-budgie:~# lsmod | grep -i rt
rt2800usb              28672  0
rt2x00usb              20480  1 rt2800usb
rt2800lib              94208  1 rt2800usb
rt2x00lib              53248  3 rt2800lib,rt2800usb,rt2x00usb
mac80211              778240  3 rt2800lib,rt2x00lib,rt2x00usb
cfg80211              589824  2 rt2x00lib,mac80211
parport_pc             32768  0
parport                49152  3 lp,parport_pc,ppdev

**howefield** · February 27th, 2017

Moved to the "Ubuntu/Debian BASED" forum and code tags added to the OP.

**davidmohammed** · February 28th, 2017

@howefield - wrong forum - should be here https://ubuntuforums.org/forumdisplay.php?f=427

**howefield** · February 28th, 2017

@davidmohammed - correct forum.

Ubuntu Specialised Support
Specialised categories of support for the recognised Ubuntu flavours: Ubuntu, Kubuntu, Xubuntu, Edubuntu, Lubuntu, UbuntuGnome, Ubuntu Studio, Mythbuntu, Ubuntu Mate, and Ubuntu Kylin.

With the release of 17.04 Ubuntu Budgie will be added to the above tagline for the main support forums.

Good to see you here, perhaps you can give the OP some advice.

**davidmohammed** · February 28th, 2017

@howefield - this is not a flavour specific issue - probably something to-do with the 4.10 kernel at a guess. As the OP mentioned this affects Kubuntu as well. Those that hang out in development 17.04 forum would be a better bet here.

**cariboo** · March 1st, 2017

Moved to here, for quicker help.

**ventrical** · March 1st, 2017

Originally Posted by samuelkenno

Hello.

I ran the Ubuntu 17.04 from USB stick. in order to test it.

Wifi works normally out of the box in Kubuntu 16.04 and 16.10 but not in 17.04.

However I am unable to connect to any wifi network. I'm able to scan the wifi networks around but it happens an error when I try to connect.

I tested also in Kubuntu 17.04 same problem. I already collected some information that could be useful.

I think this might be important to fix before release once this might affect other ubuntu users.

16.04 release presented this very same problem. You have to go into network connections, open a wireless instance, and enter your WEP. I forget exactly what the bug was.

Regards..