Comment 45 for bug 274405

You are right, I am certain that it is more involved than a single line of code. It seems that NM is not scanning for new networks automatically after a resume, but only on it's usual timed schedule, and I would expect it to be simple enough to trigger this kind of a scan through a dbus signal when resuming or something. (see http://www.nabble.com/Export-%22scan-now%22-command-over-D-Bus-td22731714.html) It may also be that wpa_supplicant is actually at fault, since I believe NM is relying on this for scanning. I have not looked at the code at all, however.