Network Manager becomes confused by sleep

[Bogdan Butnaru]

Hello! I'm using Gutsy on a laptop with an ipw3945 WiFi card.

I've noticed some weird behavior of the Network Manager when resuming from sleep. I'm connected at home to a WPA2 network, which seems to work very well. However, when I resume the computer from sleep,

1) The nm-applet remains stuck in a state where
  (a) it displays the wireless icon with full connectivity (all bars on),
  (b) it doesn't respond to any commands (I've tried disabling and re-enabling the wireless, nothing seems to happen).
2) Sometimes I've seen the NetworkManager take up 100% of one CPU (it's a dual-core machine), but I can't figure out what's happening, nothing appears in any log I've looked at.

Once I've even seen the WiFi interface attached to my AP, an IP is set-up, but the network didn't work. By the way, I've been connecting to an unprotected AP (neither WEP nor WPA), and this didn't happen; when resuming from sleep the network started working right away.

So far the only solution I've seen is rebooting. Isn't there any way of debugging this further, to find out where the issue is? It's very reproducible (it happened every time I tried, with some differences in behavior), I just don't know where to look for trouble.

[solidd (solidd-swa)]

i would like to confirm this behavior with my travelmate 2420 with a ipw2200 driver for my wireless chip.

any solutions yet?

[Michael Elkins (sigpipe)]

I experience similar behavior on a Dell D610 laptop with the ipw2200 driver connected to a WPA2 network. I have not tested using just plain WEP.

Sometimes I can get the network working without totally needing to reboot, and sometimes not. What I try to do is:
# killall -9 NetworkManager
# /etc/init.d/dbus stop
ubuntu$ gnome-keyring-manager
# /etc/init.d/dbus start

I restart dbus to get NetworkManager back into shape.
gnome-keyring-manager has to be restarted as my desktop user otherwise when network-manager restarts, it will asks for the WPA2 key again because it can't access the previously stored values.

[tiwag (tiwag-gmx)]

thanks Michael for the info about how to get past the keyring-manager issue !

[kvpetrov (kvpetrov)]

Wanted to verify that I experience the same problem on my Toshiba m200 laptop. After the laptop wakes up I have to kill Network manager and run
/usr/sbin/NetworkManager
which generatlly fixes the problem... but it is really annoying.

[Przemek K. (azrael)]

I sometimes have a similar problem on my HP Compaq nx6325 (Broadcom 4310 with ndiswrapper) - it happens after frequent sleep/resume cycles. The solution is to kill NetworkManager, NetworkManagerDispatcher and nm-applet and start them again.

[Andreas Schildbach (schildbach)]

This is most probably a dupe of bug 154254.

[Andreas Schildbach (schildbach)]

You should probably try network-manager 0.6.5-0ubuntu16.7.10.0, which is available in gutsy-proposed. Is the problem still there?

[Bogdan Butnaru (bogdanb)]

I've just installed it, I'll see how it works.

However, I stopped seeing the exact behavior mentioned at the top of this report for some time. The WiFi is re-connected on resume _some_ times, though not always. I still get weird behavior on some resumes, which I've documented in some other reports.

You can close this as far as I'm concerned (I'll drop a note if I see it again), but there were other users who reported seeing it above, maybe they still have it.

[Matthew Woerly (nattgew)]

I'll go ahead and mark this as Invalid according to the previous comment by the initial reporter. Feel free to re-open if you find you still have this issue.