FWIW, several months ago I got fed up and hacked around this by just commenting out a key schedule_scan call in NetworkManager..... I no longer have the problem, but I have to manually "sudo iwlist ath0 scan" on boot or when roaming to another location for NetworkManager to see any [new] networks.
Makes one want to implement a dbus call (?) for a "Scan Network" menu click in nm-applet. I'm not sure what this means as for doing a _real_ fix, but I'll take my Tylenol to mask the headache for now. -- Again, doing "sudo iwlist ath0 scan" makes my system exhibit the *same* symptoms as when "roamed to (none) ((none))" use to pop up (try it yourself), so I have to believe the root problem is really with the driver and/or common linux wireless stack. Also, I don't recall having this problem with the old ath_pci driver, just this new ath5k one. Also, wicd does not appear to do any periodic scanning, thus does not exhibit the nasty behavior. ** Attachment added: "network-manager_no-auto-scan.patch" http://launchpadlibrarian.net/30894485/network-manager_no-auto-scan.patch -- network-manager roams to (none) ((none)) - background scanning https://bugs.launchpad.net/bugs/291760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
