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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1425760
Title:
NM takes a long time to discover and connect to wifi after
suspend/resume and roaming
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1425760/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
