Comment 12 for bug 876822

Mark,

Actually, it's a likely scenario that after the killswitch was enabled and disabled again, the driver might end up in the wrong state, blocking scanning results.

Carla,

Once wireless is re-enabled, does it list something like "Device not ready"? Or just nothing listed under it at all? I looked at the logs quickly and I could only find instances of your tests where wireless was re-enabled only for a few seconds before using your workaround. It would be more helpful if you could confirm you've waited at least a minute before killing off networking completely, just in case it takes a little bit of time before the driver triggers a scan.