nm-applet needs restart after resume

[Michael Nelson]

STR:
1) Resume from suspend, nm-applet displays no network connection (that has been the case on this computer for a long while, other computers on my network reconnect automatically)
2) Click on nm-applet and select the network

ER:
 * nm applet starts animating and connects
AR:
 * Nothing happens. I need to `pkill nm-applet && nm-applet &`, then I can choose my network and continue.

I'm not sure when it started, I think only a few days ago

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CheckboxSubmission: f26299558349e6bfa9a64225e1770925
CheckboxSystem: 669b662da410063cc918e0f60cf6cddf
Date: Thu Feb 16 08:45:17 2012
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
IpRoute:
 default via 192.168.1.1 dev wlan0 proto static
 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
 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.10 metric 2
 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to precise on 2012-01-16 (30 days ago)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.3.0 connected enabled enabled enabled enabled enabled

[Michael Nelson (michael.nelson)]

This was happening consistently when I reported the bug, but since updating a few days ago, I've only noticed it once out of 4 or 5 suspends.

[Mathieu Trudel-Lapierre (cyphermox)]

I can't reproduce this at all. Michael, can you still notice this issue with an updated network-manager-gnome package?

[Kapil Thangavelu (hazmat)]

i've noticed this a few dozen times on precise. effectively the nm applet is reporting output of the network status correctly but doesn't process any inputs. i typically just startup a second nm-applet, which does respond to input, select the network. At this point both applets will show the proper animation and reflect the current network device, after which i go ahead and kill the second applet. The original applet will continue to be non-responsive to inputs though.

[Kapil Thangavelu (hazmat)]

Re reproducing its not a simple matter of just waking from sleep, but i've talked to several other folks at uds that this has happened to on a regular basis.

[Michael Nelson (michael.nelson)]

@mathieu-tl - Since my comment above (comment 2 on 2012-02-23) I have not seen the original issue that I reported. There have been a few times where I thought my machine wasn't going to connect after a resume, but it always began animating before I'd been able to pkill nm-applet.

Is there info you can request hazmat or others to attach when they see it again (related to the initial nm-applet instance)?

[Eloy Paris (peloy-chapus)]

#985028 could be a duplicate of this bug.

I do not think the problem is related to suspend-resume cycles but rather to the scanning and discovery of wireless networks that typically happens during suspend-resume cycles.

[Eloy Paris (peloy-chapus)]

This bug could be a duplicate of bug #930563, since bug #930563 was reported first and seems to be the same issue.

[Romano Giannetti (romano-giannetti)]

I have the same issue; not at every suspend cycle but quite often. In my case, the network seems connected but dont't work (no DNS, no connectivity). A

sudo restart network-manager

fixes the problem. I do not think that the bugs cited in #7 or #8 are duplicate, this is a different bug.

[Johan Svensson (ubuntu-js)]

I'm affected since 11.04 I think, and still affected in 12.10. ThinkPad x220 (was also affected on my x301, Ubuntu 12.04).

Can mention that I often switch network type manually, as I use builtin 3G modem on the run, network cable at work and wireless at home.

[Aaron Burt (aaron-bavariati)]

I'm seeing the same behaviour as Hazmat, with 12.04 on an Acer Aspire One 722 with an AR9285 WiFi NIC.
After some number of suspend/resume cycles, nm-applet responds to user input, but does not actually act on it.
It goes back to working correctly if I kill and restart it. Has nothing to do with the NM daemon, just the applet.

[oriolpont (oriolpont)]

Aaron, this bug has been fixed in a recent update. Maybe you are experiencing bug #1011073 which is fixed in precise-proposed and the fix should be in updates soon.