after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects.

Bug #1603815 reported by Miguel Fernandez on 2016-07-17
44
This bug affects 9 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Critical
Unassigned

Bug Description

after updating to ubuntu 16.04 the network manager is unable to connect me to the wifi network. I can see the network, but once I introduce the password, it asks me for the password after a few seconds and never connects. I use different devices connected to the same wifi so it is not a problem of writting the wrong password.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Jul 17 16:58:17 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-16 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.2.1 dev enp2s0 proto static metric 100
 169.254.0.0/16 dev enp2s0 scope link metric 1000
 192.168.2.0/24 dev enp2s0 proto kernel scope link src 192.168.2.242 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
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
 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes 4294966297 no /org/freedesktop/NetworkManager/Settings/2 yes enp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1
 BELL419 2 8bd64cc4-181f-449b-95a3-edc74cf2a9a6 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
 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13 /org/freedesktop/NetworkManager/ActiveConnection/1
 wlp3s0b1 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Miguel Fernandez (flexo-ast) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in network-manager (Ubuntu):
status: New → Confirmed
Changed in network-manager (Ubuntu):
importance: Undecided → Critical
Luke (delosisigh1) on 2016-12-02
description: updated

Can you check the password in network-manager view and edit it there?

I think that the "wrong password - enter new"-dialog does not save the entered password and thus a reconnect with the old wrong password always fails.
See also Bug #1542733 which I have experienced together with this one.

Download full text (3.9 KiB)

sorry, I gave up and I gave the laptop to a family member who is going to
reinstall an OS.

Miguel

On 3 January 2017 at 11:42, Michael Mess <email address hidden> wrote:

> Can you check the password in network-manager view and edit it there?
>
> I think that the "wrong password - enter new"-dialog does not save the
> entered password and thus a reconnect with the old wrong password always
> fails.
> See also Bug #1542733 which I have experienced together with this one.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1603815
>
> Title:
> after updating to ubuntu 16.04 the network manager is unable to
> connect me to the wifi network. I can see the network, but once I
> introduce the password, it asks me for the password after a few
> seconds and never connects.
>
> Status in network-manager package in Ubuntu:
> Confirmed
>
> Bug description:
> after updating to ubuntu 16.04 the network manager is unable to
> connect me to the wifi network. I can see the network, but once I
> introduce the password, it asks me for the password after a few
> seconds and never connects. I use different devices connected to the
> same wifi so it is not a problem of writting the wrong password.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: network-manager 1.1.93-0ubuntu4
> ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
> Uname: Linux 4.4.0-31-generic x86_64
> ApportVersion: 2.20.1-0ubuntu2.1
> Architecture: amd64
> CurrentDesktop: Unity
> Date: Sun Jul 17 16:58:17 2016
> IfupdownConfig:
> # interfaces(5) file used by ifup(8) and ifdown(8)
> auto lo
> iface lo inet loopback
> InstallationDate: Installed on 2016-07-16 (1 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
> IpRoute:
> default via 192.168.2.1 dev enp2s0 proto static metric 100
> 169.254.0.0/16 dev enp2s0 scope link metric 1000
> 192.168.2.0/24 dev enp2s0 proto kernel scope link src
> 192.168.2.242 metric 100
> NetworkManager.state:
> [main]
> NetworkingEnabled=true
> WirelessEnabled=true
> WWANEnabled=true
> SourcePackage: network-manager
> 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
> Conexión cableada 1 9e376788-1744-46de-a314-eeb07aad8c13
> 802-3-ethernet 1468789026 dom 17 jul 2016 16:57:06 CDT yes
> 4294966297 no /org/freedesktop/NetworkManager/Settings/2
> yes enp2s0 activated /org/freedesktop/NetworkManager/
> ActiveConnection/1
> BELL419 2 8bd64cc4-181f-449b-95a3-edc74cf2a9a6
> 802-11-wireless 0 never yes 0
> no /org/freedesktop/NetworkManager/Settings/1
> no -- -- --
> nmcli-dev:
> DEVICE TYPE STATE DBUS-PATH
> CONNECTION CON-UUID ...

Read more...

Uwe (gandalf.the.grey) wrote :

I'm experiencing the same problem after I have changed my WiFi router. Each of my device connect flawlessly except a laptop running Ubuntu 16.04. I was only able to connect to my network after disabling the NetworkManager and configuring WiFi using wpa_supplicant.

openfred (openfred) wrote :

Strangely enough, no issue on Fedora 27 or Debian 9 Jessie nor Debian 10 Buster.
Really strange, considering Ubuntu 18.04 is based on Debian 10 !!!

After comparing many files, it appears that the 2 last files of /etc/NetworkManager/NetworkManager.conf have been added on Ubuntu !

Debian 10:
    cat /NetworkManager/NetworkManager.conf
    [main]
    plugins=ifupdown,keyfile

    [ifupdown]
    managed=false

Ubuntu 18.04:
cat /etc/NetworkManager/NetworkManager.conf
    [main]
    plugins=ifupdown,keyfile

    [ifupdown]
    managed=false

    [device]
    wifi.scan-rand-mac-address=no

I removed this 2 files, and now Wifi works perfectly. The wifi passphrase is accepted, and even going to sleep mode and back is fine.

------
I would strongly recommend to modify /etc/NetworkManager/NetworkManager in package network-manager to remove the 2 last lines. In fact this file should not be modified by Ubuntu and kept as in Debian.
Is it possible to do it in Ubuntu before 18.04 LTS to be launched ???
------

It seems this 2 lines have been added due to bug 1681513:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513
As reported here:
https://askubuntu.com/questions/905283/wifi-issue-with-ubuntu-17-04

By the way, file NetworkManager.conf is empty in Fedora.

Cheers
Fred

Uwe (gandalf.the.grey) wrote :

Thanks for your efforts, Fred, but unfortunately, this does not work for Ubuntu 16.04 or Mint 18.2, because the two lines you found does not exist there. The NetworkManger.conf looks exactly the same as on Debian. Hopefully, the error won't exist anymore on the next Ubuntu and Mint version, respectively! ;-)

Cheers

Uwe

openfred (openfred) wrote :

It is still present on Ubuntu 18.04, I filled a bug: 1762152
But unfortunately, I've not been able to link this bug to Bionic, and it seems that it's going to be released with the bug. Unfortunately.

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

Other bug subscribers