Comment 1 for bug 462625

As an experiment, I've left the ad hoc network I created last week in its default state (i.e., "automatically connect", etc.).

Despite regularly being in locations where known infrastructure networks are available, network manager so far ALWAYS goes with the ad hoc network after resuming from suspend. I have to manually select the infrastructure network every time. (Annoyingly, scan results and reconnecting seems to be extra slow and glitchy after the ad hoc network has been activated. But that's a different bug. Maybe in the driver.)

Network manager certainly ought to have enough data at this point to keep track of my manual corrections and build up a priority list. Perhaps the trouble is that ad hoc networks are by definition always available, so network manager sees this and connects instantly after resume, before external scan results have even had a chance to filter in?