It looks like this bug was introduced in Ubuntu when the rebase to NM
0.9.10.0 occurred.
The function supplicant_iface_scan_done_cb is missing a call to
schedule_scan() which exists in the 0.9.8.x version of NM in utopic. It
looks to me like the patch cull_aps_on_scan_done_signal.patch got
mangled and lost its call to schedule_scan(). Furthermore, when this
patch got re-worked and copied into the patch 0002-wifi-cull-the-scan-
list-before-signalling-ScanDone-b.patch, the same mistake was carried
over. I checked and all of the upstream releases of NM still have a
schedule_scan() present in this function.
Here's a diff of the cull_aps_on_scan_done_signal.patch from NM 0.9.10.0
to the older 0.9.8.X version:
espy@shrike:% diff cull_aps_on_scan_done_signal.patch
~/dev/nm/nm-utopic-save/debian/patches/
10,14c10
< ---
< src/devices/wifi/nm-device-wifi.c | 29 ++++++++++++++++++++++++-----
< 1 file changed, 24 insertions(+), 5 deletions(-)
<
< Index: b/src/devices/wifi/nm-device-wifi.c
---
> Index: network-manager-0.9.8.8/src/nm-device-wifi.c
16,18c12,14
< --- a/src/devices/wifi/nm-device-wifi.c
< +++ b/src/devices/wifi/nm-device-wifi.c
< @@ -183,6 +183,10 @@ static void supplicant_iface_notify_scan
---
> --- network-manager-0.9.8.8.orig/src/nm-device-wifi.c
> +++ network-manager-0.9.8.8/src/nm-device-wifi.c
> @@ -200,6 +200,10 @@ static void supplicant_iface_notify_scan
29c25
< @@ -1609,14 +1613,20 @@ supplicant_iface_scan_done_cb (NMSupplic
---
> @@ -1810,14 +1814,22 @@ supplicant_iface_scan_done_cb (NMSupplic
50a47,50
> +
> + schedule_scan (self, success);
> }
>
52,54c52
< if (priv->requested_scan) {
< priv->requested_scan = FALSE;
< @@ -1836,13 +1846,22 @@ cull_scan_list (NMDeviceWifi *self)
---
> @@ -2005,13 +2017,22 @@ cull_scan_list (NMDeviceWifi *self)
I'll rebuild with the line restored and report results.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1445134
Title:
Network manager never scanning for new access points
Status in Canonical System Image:
Confirmed
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
While trying to reproduce another bug related with the last seen value
from the access points, I noticed that network manager is never really
scanning for new access points on my desktop, not even when not
connected.
$ sudo nmcli g logging level debug domains wifi_scan
Then powered an access point, but was never really able to see it.
From syslog, noticed that there is never really a scan, which explains
why the ap never goes away and why it is not able to find it in the
first place.
If I force a scan via cmdline it works as expected (and I noticed a
scan also happens when changing connections).
Was also able to reproduce this issue on mako, with the following image:
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 173
device name: mako
channel: ubuntu-touch/devel-proposed
alias: ubuntu-touch/vivid-proposed
last update: 2015-04-16 14:58:58
version version: 173
version ubuntu: 20150416
version device: 20150210
version custom: 20150416
In the mako case, I booted with a known connection in place, it
connected successfully but it never really scans for other access
points. Scan works fine after disconnecting though.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: network-manager 0.9.10.0-4ubuntu14
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
ApportVersion: 2.17.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Apr 16 14:21:42 2015
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-10-29 (534 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
IpRoute:
default via 192.168.1.1 dev wlan0 proto static metric 1024
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
169.254.0.0/16 dev lxcbr0 scope link metric 1000
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16
SourcePackage: network-manager
UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago)
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2013-11-04T02:19:36.923463
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code
2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
