NM can't connect to another, known, Wi-Fi network after resume from suspend; reboot fixes it

Bug #1012154 reported by Teo
This bug report is a duplicate of:  Bug #780602: nm-applet leaks memory. Edit Remove
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Usually I connect to wifi networks just fine.

Now I suspended (while I was connected to a network) and moved the computer to another place.

When I resumed, the icon in the notification area correctly displayed that it was disconnected. The network to which I was connected prior to suspend was not available and there were other networks available.

When I selected one of the available newtorks (one to which I often connect and whose password is stored) nothing happened: it didn't even try to connect. I tried several times with the same result: it would just do nothing.
I also tried to connect to different network, and _nothing_ happened (it should have prompted me for password).

Rebooting fixed the issue.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.4.0-0ubuntu4.1
ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
Uname: Linux 3.2.0-25-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu9
Architecture: i386
CRDA:
 country ES:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (N/A, 20)
  (5250 - 5330 @ 40), (N/A, 20), DFS
  (5490 - 5710 @ 40), (N/A, 27), DFS
Date: Tue Jun 12 16:19:57 2012
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static
 169.254.0.0/16 dev wlan0 scope link metric 1000
 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.54 metric 2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-05-17 (25 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.4.0 connected enabled enabled enabled enabled disabled

Revision history for this message
Teo (teo1978) wrote :
Thomas Hood (jdthood)
summary: - can't connect to any network after suspend/resume
+ NM can't connect to another, known, Wi-Fi network after resume from
+ suspend; reboot fixes it
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Thomas Hood (jdthood)
Changed in network-manager (Ubuntu):
status: Confirmed → New
Revision history for this message
Teo (teo1978) wrote :
Revision history for this message
Thomas Hood (jdthood) wrote :

#1019395 reports similar behavior "at random times", not after resume, so it *may* not be a duplicate.

Revision history for this message
Thomas Hood (jdthood) wrote :

If #1011073 happens on resume then this (#1012154) should be linked with that (bug #1011073).

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

This is basically the same kind of issue as bug 1019395. Marking as a duplicate.

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.