This sounds to me like an issue with the supplicant or directly with the
wireless driver, but to be certain, could you guys please do a clean
boot, use the computer normally and put it to suspend for the night,
then once you resume it attach the contents of /var/log/syslog (and/or
syslog.1 or others, if you can find at which point in those files the
system boots) to this bug? I don't see any message from NetworkManager
in the logs currently attached, though it's clear it was sent after to
standby/resume attempts.
With this, and provided NetworkManager then logs the supplicant state
changes, it should be pretty clear with that and the message from the
kernel what exactly is going on.
@wch: Please also confirm which driver you use -- Justin's report
mentions wl, which would show as "STA" in jockey (the restricted drivers
configuration panel in System->Administration). If you don't use the
same driver, it may be a different issue or an indication that NM is the
culprit :)
Thanks!
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
--
System takes too long to activate wifi on resume
https://bugs.launchpad.net/bugs/665944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
