desktop-packages team mailing list archive

[Mathieu Trudel-Lapierre <mathieu.tl@xxxxxxxxx>]

Do you remember which network you were suspending on at that point?

I see some fairly old scan results, but nothing extraordinary (4, 14, 24
seconds, which seems consistent with NM's scanning thresholds). Still,
the timing is such that there may have been a scan request or an
automatic scan by the driver before the command was run. Could you
attach a full syslog (or at least, containing kernel, wpasupplicant and
NetworkManager messages) so that we know whether wpasupplicant has
received scan results and when?

For lack of better options right now, it looks like this might "just" be
stale scan results from the driver, but I'm also not noticing this kind
of behavior on my very similar system.

** Changed in: network-manager (Ubuntu)
       Status: New => Incomplete

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

-- 
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/1425760

Title:
  NM takes a long time to discover and connect to wifi after
  suspend/resume and roaming

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  Starting around the time of the upload of NM 0.9.10.0, when suspending
  my laptop and roaming between locations, NM has started taking a long
  time to find the networks in the new location and connect to known
  essids.

  Syslog to be attached.

  Note that the first essid it tries to roam to, "Google Starbucks", is
  not present in either the pre-suspend location or the post-resume
  roamed location.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu6
  ProcVersionSignature: Ubuntu 3.18.0-8.9-generic 3.18.1
  Uname: Linux 3.18.0-8-generic x86_64
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 25 15:18:10 2015
  InstallationDate: Installed on 2010-09-24 (1615 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
  IpRoute:
   default via 192.168.1.1 dev wlan2  proto static  metric 1024 
   169.254.0.0/16 dev vnet0  scope link  metric 1000 
   192.168.1.0/24 dev wlan2  proto kernel  scope link  src 192.168.1.127 
   192.168.122.0/24 dev virbr0  proto kernel  scope link  src 192.168.122.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WWanEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (81 days ago)
  WifiSyslog:
   
  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/ubuntu/+source/network-manager/+bug/1425760/+subscriptions