On Tue, Apr 28, 2009 at 02:37:55PM -0000, Dan Langlois wrote: > Just to recap: > If you're affected by this bug, then you'll find that your desired AP doesn't > show up in the list of available networks. You'll find yourself wanting a > refresh/rescan button (because you know it's there). After several minutes > of waiting patiently, you're AP *may* finally appear and you'll connect. > With this patch, your AP should always appear and connect immediately. > > I tried to suggest a low-impact patch. I can't see how this patch could > break anything, in fact, it fixes something. I discussed this on the NM > list to see if anyone could find any fault with it, no red flags. I > agree it should be verified by a few more people just to be sure, but > I'd hardly call it delicate. >
The only regression potential i see here is for drivers that need between 8-10 seconds to get their results collected. Those that need that much time are probably flaky anyway and I don't think we have considerable regression potential here. - Alexander -- network manager 0.6 should use 9 or 8 seconds as a scan timeout to workaround driver bugs https://bugs.launchpad.net/bugs/361602 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
