Ubuntu
network-manager package

Network manager stopped scanning for wifi networks

Bug #1332904 reported by Dima Ryazanov on 2014-06-22

22

This bug affects 4 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

After I resumed my laptop from suspend, it would not connect to wifi. For a while, it seemed confused about its connection state, then it displayed "disconnected", and showed that there were no wifi networks available (which is not true).

To debug the problem, I ran "nmcli d wifi list", which showed no results.
Then I ran "iwlist scan", which also showed no results.
Then I tried "sudo iwlist scan" - which showed all the wifi networks, and actually caused the network manager to start working again. It connected to a network successfully, and so on.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: network-manager 0.9.8.8-0ubuntu7
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Jun 21 22:12:35 2014
EcryptfsInUse: Yes
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-04-05 (443 days ago)
InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.34 metric 9
SourcePackage: network-manager
UpgradeStatus: Upgraded to trusty on 2014-05-14 (39 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.8 connected enabled enabled enabled enabled disabled

Tags:

Revision history for this message

Dima Ryazanov (dima-gmail) wrote on 2014-06-22:

#1

CRDA.txt Edit (257 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (656 bytes, text/plain; charset="utf-8")
IwConfig.txt Edit (474 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (189 bytes, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (634 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (75 bytes, text/plain; charset="utf-8")
NetworkManager.state.txt Edit (104 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (592 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (103 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (113 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (160.9 KiB, text/plain; charset="utf-8")
nmcli-con.txt Edit (9.0 KiB, text/plain; charset="utf-8")

Revision history for this message

goliy (musor-zdes) wrote on 2015-08-14:

#2

It happens not very often with me, usually when I reboot Access Point and Ubuntu just don't want to find AP again. When I turn off and turn on wifi - no networks at all.
Whank you for temp solution: "sudo iwlist scan" works much better then reboot =)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-09-02:

#3

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

Changed in network-manager (Ubuntu):
status:	New → Confirmed

Revision history for this message

teo1978 (teo8976) wrote on 2015-09-02:

#4

I have also observed this. And it was not after suspending and resuming. I hadn't suspended/resumed since the previous boot which was just a few minutes before.

It is NOT systematic.

Usually, when I turn off and on wifi in the hardware as a workaround for bug #1491612, it does force a rescan.
This time, however, it wouldn't, even after retrying several times.

Since I didn't know about the command "iwlist scan", I had to reboot.

Revision history for this message

teo1978 (teo8976) wrote on 2015-09-02:

#5

Sorry, when I say "I turn off and on wifi in the hardware" I mean I do it with Fn+F3 on my laptop. I'm not sure how much it is really "hardware"

Revision history for this message

Shaun Crampton (fasaxc) wrote on 2016-11-19:

#6

I have the same symptom (wifi ends up disconnected after resume, cured by running a scan manually) but I'm seeing this after upgrading to 16.04.

One oddity is that network-manager often shows that it thinks it is connected to an AP after resume but it's not the correct one. It seems to think it is connected to my neighbour's AP, for example. I wondered if the APs had swapped channels due to autodetection or something.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.