Fix silly "Networking Disabled" issue (Ubuntu 10.04)

gistfile1.sh

su root
# Don't you hate when you need to root to fix dumb issues?
service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start
reboot -h now

8 years later, ubuntu 18.04, this is still a thing.
thank you!

Man, I was struggling with this for about 3 hours.
Thaaaaaank yoooouuuu!!!

Thank you. There are lots of unnecessary solutions on other platforms.

Thank you soo much!! It worked!

This tricks still working even though ubuntu 18.04!!! Thank you so much

9 years old but still it worked for me thanks a lot!!!

Ubuntu 20 and nothing worked except this one. GOD bless you.

This is life saver. Thanks a lot.

I am on Ubuntu 20 and all my wireless network adapters were disabled. This was the only thing that actually worked! Thank you so much!!!!

Ubuntu 18.04, and this solution worked perfectly. Thank you so much!.

I've wasted hours on this, and your gist fixed it immediately. Thanks!

This worked for me!

The only thing, is I keep having to do this almost everyday and its getting annoying. But I am not familiar with this stuff and am at a loss on how to trouble shoot it. Any suggestions?

Thank you so much!! I've been looking everywhere and this did it!

jfc aaaaaand this still works for 20.04.

Ubuntu 18.04, helped fix "lshw / *network-DISABLED" issues after compiling ethernet driver

Thank you so much!! I have been struggling for it almost 3 hours. Btw, if you faced an authentication error in the first line, try using "sudo -i"

2022 still works, thank you man

Thanks! It still worked for ubuntu 22.04 ...

Just a small change:
service network-manager stop ---> service NetworkManager stop
service network-manager start ----> service NetworkManager start

ubuntu 18.04, unfortunately, didn't solve this for me :(
the best luck to all who see this.
Network is disabled under "lshw -c Network"

11 Years later, your contribution is still saving lives.
It worked for me on Ubuntu 22.04.

11 years later still saves lives

11 years later ... well done ubuntu!

Still works in 2023!

thanks to kanhaiya-2000's comment this still works on Ubuntu 22.04 in 2023!

still works! I wonder if it will work in another 12 years

still works! I wonder if it will work in another 12 years

believe me it'll

This didn't help rather installing the 'netplan.io' package fixed this issue (Ubuntu 22.04.3 LTS).

How did I get into this scenario?
Well, I tried 'apt auto-remove python3', and all of a sudden my machine rebooted and landed on the tty1 prompt, couldn't start ubuntu-desktop!

How did I get back to ubuntu-desktop?
Ran 'sudo apt install --reinstall ubuntu-desktop' and got back the GUI. But then the ethernet was not working, 'lshw -c network' showed my ethernet interface 'enp43s0' was unmanaged!

sudo apt install netplan.io
sudo apt install network-manager

sudo cat /var/lib/NetworkManager/NetworkManager.state
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true

in my case, no need to delete NetworkManager.state

I cannot believe this thing still works in 2024...

It is 2026, and the broken NetworkManager.state file is still an issue! After removing that file fixed everything, I figured out that I could have solved the problem without becoming root using:

$ nmcli net on

But, there's no way for anyone to ever figure that out as NetworkManager never mentions the NET setting!

• In the Gnome Settings GUI, the Wi-Fi panel simply said, "No Wi-Fi Adapter Found"
• From the command line, nmcli dev wifi failed to scan for stations but gave no error messages.
• nmcli, nmcli dev, and nmcli general all showed that wlan0 was unmanaged which was not true and a red herring. The more important fact was that "NET" was disabled and so being managed or not didn't matter and could not be changed.
• Trying nmcli dev set wlan0 managed yes gave no error message even though it failed because NET was off.
• nmcli radio said that WIFI was disabled, which was true, but irrelevant since it cannot be changed when NET is off.
• Trying nmcli radio wifi on gave no error message even though it, too, failed to work.

Thank goodness I ran across this gist as I was tearing my hair out.