nm-applet says "network disabled" on first startup/login after a failed hibernate

[Stephen Warren]

Under lucid, my laptop won't hibernate properly; it hangs pretty soon after starting the hibernate process, and I eventually just have to power off the system.

The first time I boot the system after this, and log in, nm-applet says "network disabled", and I have to right-click the NM icon and select "enable networking". After this, networking starts up OK (it associates with my wireless).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager-gnome 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Thu Apr 8 20:59:46 2010
IfupdownConfig:
 auto lo
 iface lo inet loopback
InterestingModules: b44
IpRoute:
 192.168.62.0/24 dev eth1 proto kernel scope link src 192.168.62.20 metric 2
 169.254.0.0/16 dev eth1 scope link metric 1000
 default via 192.168.62.1 dev eth1 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager-applet
WpaSupplicantLog:

[Stephen Warren (srwarren)]

FYI, the hibernate issue is bug 558927, in case it gives clues where in the hibernate process things fail which might give clues to the NM issue.

[Andrei Bordei (andrei-bordei)]

Same thing for me on HP 6715b

[Davor Cubranic (cubranic)]

This could be the same issue as mentioned in comment #4 of bug #524565: Debian bug 566891 (Network Management disabled after "suspend to ram"), http://osdir.com/ml/debian-bugs-dist/2010-01/msg07864.html

[Davor Cubranic (cubranic)]

Seems a duplicate of bug #524565.

[Mathieu Trudel-Lapierre (cyphermox)]

Yup, as mentioned before, this is a duplicate of 524565, let's mark it as such.

[Mathieu Trudel-Lapierre (cyphermox)]

I did this all wrong, not the right bug.

[Davor Cubranic (cubranic)]

How is it different from #524565 then?

[Mathieu Trudel-Lapierre (cyphermox)]

DavorCubranic: 524565 mentions network is enabled but cannot be connected to, and suspend triggers itself -- not the case here: networking is disabled after suspend (and is not according to the info we have from the reporter in the other bug). This is a bug that affects Lucid (for which there are many duplicates though I haven't found the bug number yet), and which has been fixed in the current development release - Maverick Meerkat.

It does however seem to be the same as bdo 566891.

[Davor Cubranic (cubranic)]

You're right Mathieu, the original bug description is clearly different, my bad. I was remembering subsequent comments (from crysys & olksy), which sound like their bug is really this one.