** Also affects: network-manager (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: network-manager (Ubuntu Vivid)
Status: New => Confirmed
** Changed in: network-manager (Ubuntu Vivid)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu Vivid)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
** Changed in: network-manager (Ubuntu Vivid)
Assignee: Mathieu Trudel-Lapierre (mathieu-tl) => Tony Espy (awe)
--
You received this bug notification because you are a member of Desktop
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
Status in network-manager source package in Vivid:
Confirmed
Status in network-manager package in Ubuntu RTM:
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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
