Ubuntu – Clean install ubuntu 16.04 cannot connect to wifi using NetworkManager, but nmtui works

16.04asusnetwork-managernetworkingwireless

I've performed a fresh installation of Ubuntu 16.04 on my Asus N56VZ. Sadly, i cannot connect to wireless networks using the NetworkManager. I am able to see wireless networks, though.

I tried to connect to my network using the GUI and entered my password. But after that, nothing happens. I see no attempt to connect to this network, and I don't get an error either. I can see that the network manager saved my network, and I double and triple-checked whether the password and all other configurable parameters are correct.

Funny thing is – I am able to connect using nmtui without any problems.

I have not been able to test whether this is a problem with this specific network or if it is a general problem. I highly suspect the latter though, as I had no problem using said network on Ubuntu 15.04.

Output of some interesting commands:

Before connecting using nmtui:

iwconfig

enp4s0    no wireless extensions.

lo        no wireless extensions.

wlp3s0    IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=0 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off

lspci -vvnn | grep Network

03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
    Subsystem: AzureWave AR9485 Wireless Network Adapter [1a3b:2c97]

sudo service NetworkManager status (after I tried and failed to establish a connectiong using the NetworkManager)

● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since So 2016-04-24 00:03:32 CEST; 15min ago
 Main PID: 788 (NetworkManager)
    Tasks: 3 (limit: 512)
   CGroup: /system.slice/NetworkManager.service
           └─788 /usr/sbin/NetworkManager --no-daemon

Apr 24 00:18:24 Tesla NetworkManager[788]: <info>  [1461449904.2249] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info>  [1461449904.2253] manager: NetworkManager state is now CONNECTING
Apr 24 00:18:24 Tesla NetworkManager[788]: <info>  [1461449904.2265] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Apr 24 00:18:24 Tesla NetworkManager[788]: <info>  [1461449904.2270] device (wlp3s0): Activation: (wifi) access point 'FRITZ!Box 7362 SL' has security, but secrets are required.
Apr 24 00:18:24 Tesla NetworkManager[788]: <info>  [1461449904.2277] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn>  [1461449929.2418] device (wlp3s0): No agents were available for this request.
Apr 24 00:18:49 Tesla NetworkManager[788]: <info>  [1461449929.2419] device (wlp3s0): state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Apr 24 00:18:49 Tesla NetworkManager[788]: <info>  [1461449929.2422] manager: NetworkManager state is now DISCONNECTED
Apr 24 00:18:49 Tesla NetworkManager[788]: <warn>  [1461449929.2427] device (wlp3s0): Activation: failed for connection 'FRITZ!Box 7362 SL'
Apr 24 00:18:49 Tesla NetworkManager[788]: <info>  [1461449929.2437] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]

After connecting, iwconfig yields:

enp4s0    no wireless extensions.

lo        no wireless extensions.

wlp3s0    IEEE 802.11bgn  ESSID:"FRITZ!Box 7362 SL"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 34:31:C4:30:7D:13   
          Bit Rate=72.2 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=66/70  Signal level=-44 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:105   Missed beacon:0

I would be happy for any suggestions.

Best Answer

I have been having the same issue, While not a fix, I found that restarting the network manager works. I have included the instructions to do this below.

From the command line

Stopping Network Manager

sudo /etc/init.d/network-manager stop

Starting Network Manager

sudo /etc/init.d/network-manager start
Related Question