So I tried my experiment again, this time with a simple shell script running in root shell across a suspend/resume:
while true; do echo `date`; iwlist eth1 scan | grep hyperion done You can see where the system goes to suspend, and after resume, the original AP is no longer found. More digging needs to be done to pin this one down... ** Attachment added: "script output of cmd-line scanning during suspend/resume" http://launchpadlibrarian.net/33761843/wl-scan-s3.txt -- After Resume, NM tries to connect to previous, non-available Wi-Fi network https://bugs.launchpad.net/bugs/452571 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
