Network manager can't disconnect from wifi or connect to another wifi

Bug #1591515 reported by TyhDyh
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
High
Unassigned

Bug Description

After fresh install 16.04 I can't connect to different wifi network and if netbook lost wifi connection I need reboot it because NM can't do anything to reconnect. NM don't show connected wifi name. I attached image that show this bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.0-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CRDA:
 country BY: DFS-ETSI
  (2402 - 2482 @ 40), (N/A, 20), (N/A)
  (5170 - 5250 @ 80), (N/A, 20), (N/A)
  (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS
  (5490 - 5710 @ 160), (N/A, 27), (0 ms), DFS
CurrentDesktop: Unity
Date: Sat Jun 11 16:37:25 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-05-14 (27 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
IpRoute:
 default via 192.168.100.1 dev wlp2s0 proto static metric 600
 169.254.0.0/16 dev wlp2s0 scope link metric 1000
 192.168.100.0/24 dev wlp2s0 proto kernel scope link src 192.168.100.8 metric 600
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
 HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec 802-11-wireless 1465652043 Sat 11 Jun 2016 16:34:03 MSK yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2
 Wired connection 1 32e99c74-fafd-483a-aa6f-745655ff5e9f 802-3-ethernet 1465650077 Sat 11 Jun 2016 16:01:17 MSK yes 4294966297 no /org/freedesktop/NetworkManager/Settings/2 no -- -- --
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 HUAWEI-KpW2 3a8b63e2-b64e-4e64-b374-4fd453ccf5ec /org/freedesktop/NetworkManager/ActiveConnection/2
 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- -- --
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

Revision history for this message
TyhDyh (mybox-1-tut) wrote :
Revision history for this message
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 → High
Revision history for this message
Aron Xu (happyaron) wrote :

I wonder if you can reproduce this bug in an up-to-date version of 16.04? Can't reproduce here.

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
pgf (pgf) wrote :

i just installed xubuntu-16.04.1-desktop-amd64.iso and have seen the same (or slight variation of the same) behavior a few times over the last several days. machine is a thinkpad x220. lshw identifies the networking h/w as:
   - ethernet: 82579LM Gigabit Network Connection
   - wireless: Centrino Advanced-N 6205 [Taylor Peak]

first failure case:
   - connect to wireless network, become active network participant.
   - attach ethernet cable, become active network participant.
   - disconnect ethernet cable.
   - both wired and wireless networks were now in disconnected state, wireless did not reconnect automatically, and there was no list of networks from which to select a connection.

another failure case:
   - use laptop on wireless
   - put to sleep
   - wake laptop
   - same symptoms: both wired and wireless networks were now in disconnected state, wireless did not reconnect automatically, and there was no list of networks from which to select a connection.

this has happened several times, but note that it doesn't happen _every_ time.

when it does occur, there are two workarounds which will cause the laptop to resume normal operation:
    - sudo service NetworkManager restart
or
    - sudo iwlist scan

Revision history for this message
pgf (pgf) wrote :

i can't claim it's a dup, but this bug seems likely related to https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1585863

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

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

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