connman does not rescan for wireless networks after suspend

[Pete Goodall]

Binary package hint: connman

Steps to reproduce:
1. Connect to wireless network in location A (in this case a WEP network)
2. Close the lid to suspend the device
3. Go to location B where the original wireless network(s) is no longer available
4. Open lid to resume
5. Check wireless networks available in location B

Expected result:
Should see any wireless networks available in location B and connect to the new wireless network

Actual result:
The network indicator shows me the same wireless networks that were available in location A. Even after several hours I see the available wireless networks has not refreshed.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: connman 0.54+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-6.9-generic 2.6.35-rc3
Uname: Linux 2.6.35-6-generic i686
Architecture: i386
Date: Tue Jul 6 10:54:56 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100602.2)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: connman

[Pete Goodall (pgoodall)]

Incidentally, this can be solved by restarting the connman service.

`sudo services connman restart`

[David Barth (dbarth)]

Marking our network menu interface as "affected", as it really is, even if the bug is in the layers below.

[Joe Baker (joebaker)]

I had problems with Wifi after suspending. Try this after resuming to see if it helps:

sudo killall wpa_supplicant

wpa_supplicant will respawn.

If it works you can automate this for every suspend by creating a file such as: /etc/pm/sleep.d/99fixwifi.sh

I found parts of the following solution here:
http://fooninja.net/2010/09/02/how-to-fix-wifi-after-suspendresume-in-ubuntu/

But I modified that solution to include killing wpa_supplicant like so:

[Alf Gaida (agaida)]

really, a little bit outdated - the release for this bug is dead since years and so is the bug