connman does not rescan for wireless networks after suspend

Bug #602210 reported by Pete Goodall
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Connection Manager
Triaged
High
Unassigned
Network Menu
Invalid
Undecided
Unassigned
connman (Ubuntu)
Invalid
High
Unassigned

Bug Description

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

Revision history for this message
Pete Goodall (pgoodall) wrote :
Revision history for this message
Pete Goodall (pgoodall) wrote :

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

`sudo services connman restart`

Kalle Valo (kvalo)
Changed in connman:
status: New → Confirmed
Changed in connman (Ubuntu):
status: New → Confirmed
Revision history for this message
David Barth (dbarth) wrote :

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

Changed in indicator-network:
status: New → Confirmed
Kalle Valo (kvalo)
Changed in indicator-network:
status: Confirmed → Invalid
Changed in connman:
importance: Undecided → High
status: Confirmed → Triaged
Kalle Valo (kvalo)
Changed in connman (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → High
Revision history for this message
Joe Baker (joebaker) wrote :

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:

Revision history for this message
Alf Gaida (agaida) wrote :

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

Changed in connman (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.