Network Manager Disabled

[elivs]

The same thing happened for me on an HP 6930p laptop with kubuntu 10.04.

The settings got switched to "false" during a sleep / hibernation mode.

I can't find this in the bug tracking system, but I'm not familiar with submitting bugs to ubuntu. Has anyone submitted it yet?

elivs

[Bucky Ball]

Are these instructions for 10.04? Using 8.04 and don't have any of these files to check or change.

Should I create them and add the changes?

[dughutch]

Bump. Similar issue on Dell E6500 laptop. In the NetworkManager.state file WirelessEnabled=false happens as soon as I do service network-manager start.

[freecates]

Thanks a lot chaosgrimm.
After going back from a sleeping session on my Dell Latitude E4200, the Knetworkmanager said: "unmanaged". Both files:

/etc/NetworkManager/nm-system-settings.conf
/var/lib/NetworkManager/NetworkManager.state

had turned to "false" on

[ifupdown]
managed=false

[main]
NetworkingEnabled=false

Again thanks a lot chaosgrimm. You've saved my day

[timrichardson]

Here is my fix (this bug is reported in launchpad but it's marked low priority)
in directory /etc/pm/sleep.d as root (or with sudo)
create a file called 11_clearNetwork

#!/bin/bash
case "$1" in
    hibernate|suspend)
        #ACTION BEFORE SUSPEND/HIBERNATE
	rm /var/run/network/ifstate
	logger "deleted ifstate when suspending or hibernating"
        ;;
    thaw|resume)
        #ACTION AFTER RESUME
	rm /var/run/network/ifstate
        service network-manager stop
 	service network-manager start		
 	logger "deleted ifstate and restarted network manager"
        ;;
    *)
        ;;
esac
exit $?

[krezkey]

If the network manager isn't crashing check these, should be set as:

/etc/NetworkManager/nm-system-settings.conf

[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=true

-------
and

/var/lib/NetworkManager/NetworkManager.state

[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

Thanks for this very helpful info,but I can't seen to edit the files you have listed. what commands does a newbee like me need to know to correct these in bash and get things working again. Thanks for the help in advance.

[spiky001]

hi open termial type this in

gedit /etc/NetworkManager/nm-system-settings.conf

[guymcarthur]

Same problem on two different laptops (both Dell). This bug should be marked very high priority!

[mindaslab]

I don't know why Ubuntu guys have marked it low. This one is really serious! I became mad when I couldn't connect to Internet. This what makes Windows and Mac prevail over Ubuntu

[LifeTheHound]

I don't know why Ubuntu guys have marked it low. This one is really serious! I became mad when I couldn't connect to Internet. This what makes Windows and Mac prevail over Ubuntu

Totally agree. There's really no excuse for this level of utter incompetence.

1. Critical problem, occurred in multiple versions of Ubuntu and Kubuntu on multiple laptops.
2. Shows how ridiculously buggy things are right under the surface. It took a while to rear its ugly head, but once it did, the system was toast. So much for Linux "system security" if users have to get rid of the damn thing to use their computer again.
3. "Low priority" status on something as critical as not being able to connect to the internet is easily a display of incompetence.

I'm using Vista now. I couldn't even connect to the internet in linux to get on these forums because of this insanely critical "low priority" issue. Vista is slow, buggy, requires antivirus software, costs money, and countless other annoyances, but never a lick of problems as critical as this and many other critical "system nukes" that unfortunately comprise the mine-field of the "desktop Linux experience." There's a reason many people aren't enthusiastic about using linux -- you have to be a terminal wizard to painstakingly work around all the critical glitches. I don't want to believe that in windows this never happens because the code is particularly well written, but having the option to click on the network manager and "Diagnose and repair" is critical. Instead of screwing around with making graphics pretty and cutting "boot time," make the dang thing stable and error resilient. Even if it gets less than half of the errors of a Windows machine, Windows can fix them all somewhat easily or intuitively, and there's real recovery modes. There's no excuse for this.

The commandline tools are ridiculously fragmented, too. There's no one networking commandline. I screwed around with "ifconfig" for hours (and "iwconfig") but didn't know there was a (ridiculous) "ifup" program too, along with countless others which, quite frankly, should obviously be merged into a single intuitive program and then given a flippin' GUI.