knetworkmanager says "disabled", needs to reset networkmanager state

Bug #553994 reported by LarsIvarIgesund
118
This bug affects 22 people
Affects Status Importance Assigned to Milestone
NetworkManager
Fix Released
Wishlist
network-manager (Ubuntu)
Fix Released
Undecided
Unassigned
plasma-widget-networkmanagement (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: plasma-widget-networkmanagement

This issue cropped up a couple of days ago, after a lucid beta upgrade.

knetworkmanager is running and showing its icon in the tray, however it does nothing, only reports that "Unmanaged"/"Network Management disabled".

If connecting a cable to the ethernet port, I had to manually run dhclient to get a link, and I had to install wicd to get wireless.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager-kde 1:0.9~svn1075616-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-18.27-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-18-generic i686
Architecture: i386
Date: Fri Apr 2 16:44:58 2010
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcEnviron:
 LANGUAGE=nn_NO:nn:no_NO:no:nb_NO:nb:en
 LANG=nn_NO.UTF-8
 SHELL=/usr/bin/zsh
SourcePackage: plasma-widget-networkmanagement

Revision history for this message
LarsIvarIgesund (larsivar) wrote :
Revision history for this message
YeagDeeDs (yeagdeeds) wrote :

Same problem here. I am attempting an upgrade to see if that resolves the issue.

Revision history for this message
YeagDeeDs (yeagdeeds) wrote :

The issue is persistent after the upgrade at 5:30pm on April 3.

Revision history for this message
koso (koso) wrote :

Can you make sure you are not running any other network-manager front-end? For example check, if you have only one knetworkmanager running, also check, if there is not running service called "EXPERIMENTAL NetworkManager user ...".

Try command "nm-tool", it should show some networkmanager information.

And finally you can try to backup and remove configuration files.

Revision history for this message
YeagDeeDs (yeagdeeds) wrote :

There was a running service called EXPERIMENTAL NetworkManager (I'm not sure if this would be considered another network-manager front-end or not) however the most recent updates seem to have resolved the issue as of 11:12pm on April 5.

After running nm-tool everything now appears normal.

Thank you for the help! Maybe someday I can return or pass on the favor once I learn a little more.

Revision history for this message
LarsIvarIgesund (larsivar) wrote :

After updating packages (I didn't look into the various networkmanager versions mentioned above), it is now working better again.

Revision history for this message
Marc Cheng (bdgraue) wrote :

I use an Samsung NC10 and have the same issue. No network connection at all, so i couldn't even try to upgrade. After reading here about manually run dhclient to get a link, i plugged in lan again and run sudo dhclient. after that i made an upgrade. there are also new network-manager packages, but the problem is still there.

Revision history for this message
rww (rww-deactivatedaccount) wrote :

This just happened to me after an improper shutdown. Removing the stale NetworkManager state file:

sudo rm /var/lib/NetworkManager/NetworkManager.state

( per http://wiki.archlinux.org/index.php/NetworkManager#Network_Management_Disabled )

fixed the problem and restored functionality. In my opinion, either knetworkmanager or NetworkManager (whichever is responsible) should clear out stale state files at startup, since most other applications in the system that use state/PID files seem to be capable of doing so after an improper shutdown.

Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Cheng (bdgraue) wrote :

i could reproduce what robert wall wrote.

had the netbook on suspend over night and it lost power. in the morning i had the unmanaged network shown. moved the /var/lib/NetworkManager/NetworkManager.state to /var/lib/NetworkManager/NetworkManager.state-old and rebooted. after that it worked again.

thanks mr. wall. u saved my day :)

Revision history for this message
ivan (ivan.tg) wrote :

I had the same problem with Kubuntu 10.04 (release).
My laptop could not wake up from suspend to RAM (which was the default action on close lid). I had to restart it from the button.
In the file /var/lib/NetworkManager/NetworkManager.state i found:

NetworkingEnabled=false

After changing it to true ( as suggested here http://wwww.ubuntuforums.org/showthread.php?p=9219714 ) and restarting it worked.

Revision history for this message
sfa (sfakher) wrote :

Me too. The same problem since updating to Kubuntu 10.04 last weekend.

With these steps:

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

everything works fine again.

Revision history for this message
jph.lebrat@gmail.com (jph-lebrat) wrote :

Since march, I installed and upgraded Lucid Lynx on 3 different PC (Lenovo, Dell and Iventive) and I encountered the same problem (as described above), and the same solution has been successfully exercised.
For the Ubuntu's image, it will be very good to correct this bug, at least as Robert Wall proposes.
Thank you for Ubuntu !

Revision history for this message
YeagDeeDs (yeagdeeds) wrote :

I followed the steps outlined by sfa with no success after reboot. I have not had an improper shutdown or any problems with suspend or hibernate. It appears that we are probably describing two different, but possibly related problems.

Revision history for this message
P (p92) wrote :

exactly same problem for me on thinkpad X40
after upgrade from karmic to lucid network worked but I experienced some kernel freeze lots of times and once this problem have been fixed my network manager icon was always greyed out and unmanaged.

Removing the stale file made it work again thanks a lot !

But this is a workaround effectively showing that NetworkManager should recreate this file when it is started !

Revision history for this message
P (p92) wrote :

dpkg -l network-manager
ii network-manager 0.8-0ubuntu3

affects: plasma-widget-networkmanagement (Ubuntu) → network-manager (Ubuntu)
Changed in plasma-widget-networkmanagement (Ubuntu):
status: New → Confirmed
Revision history for this message
skierpage (skierpage) wrote :

Happens to me too, every time I have a problem in standby, shutdown, or resume. I think Bug #576154 in network-manager: “KNetworkManager can't enable networking, have to switch to GNOME to enable” is a duplicate of this.

The underlying problem in many (all?) cases with the NetworkManager.status disabling itself seems to be Bug #524454 in network-manager: “Networking is disabled on boot”.

Changed in network-manager:
status: Unknown → Confirmed
Adam Porter (alphapapa)
summary: - knetworkmanager doesn't connect with networkmanager
+ knetworkmanager says "disabled", needs to reset networkmanager state
Revision history for this message
molecule-eye (niburu1) wrote :

Sometimes if my computer crashes, or always if it crashes during a suspend (e.g. to RAM or disk), upon reboot networking is disabled. I've found that simply suspending to RAM and resuming gets networking back (assuming that this is an available option). What in the suspend script causes it to reenable networking upon wake up? One could simply run this in a terminal instead of needlessly suspending and resuming.

Revision history for this message
koso (koso) wrote :

Can confirm this problems. After start-up, networking is disabled. I can enable it using plasmoid (in maverick) but it wont work (it wont show any possible connections except saved connections). Restarting KDED module will probably help, but I haven't tested it for a longer time.

How to reproduce:

1. suspend to ram
2. shut down computer (hold down shutdown button or disconnect all power sources)

Changed in network-manager:
status: Confirmed → Unknown
Revision history for this message
LarsIvarIgesund (larsivar) wrote :

Haven't had this issue in Maverick

Revision history for this message
Shaved Wookie (shavedwookie) wrote :

I'm having this issue in maverick, however

sudo rm /var/lib/NetworkManager/*.state
sudo restart network-manager

seems to solve it until next time.

Revision history for this message
P (p92) wrote :

this has been fixed in KDE 4.5.4

Changed in network-manager:
status: Unknown → Fix Released
Changed in network-manager:
importance: Unknown → Wishlist
Revision history for this message
David H (david-houlder) wrote :

This happened to me yesterday in kubuntu 10.04. Resolved it with

service network-manager stop
rm /var/lib/NetworkManager/NetworkManager.state
service network-manager start

This is nasty - if you can't get a network connection up manually and don't have any other web access, it's very difficult to debug.

Revision history for this message
StefanF (stefan) wrote :

I did not encounter the problem anymore since a long time with newer Ubuntu versions. I think this can be closed.

Thomas Hood (jdthood)
Changed in network-manager (Ubuntu):
status: Confirmed → Fix Released
Changed in plasma-widget-networkmanagement (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
bnewtonius (brian-newtonius) wrote : Time, Money, Keeping you from earning the Degree you deserve? business media

   Hello!
   Customer

We provide a concept that will allow anyone with sufficient work experience to obtain a fully verifiable Unievrsity Dgeree. Bcahelors, Docotrate or Bachleors.

Regardless of your location, you can receive a degree in your desired field. All you need is sufficient knowledge, military, or professional experience and you are on your way to an instant degree in your relevant field.

Earn as deserved. Obtain a Dgeree!. Unlock the doors.

CALL US TODAY AND GIVE YOUR WORK EXPERIENCE THE CHANCE TO EARN YOU THE HIGHER COMPENSATION YOU DESERVE!

-------------------------
Give us a call NOW!

+ 1 - 646 - 537 - 1732
Please leave us your:
1) Your Name
2) Your Country
3) Phone No. with countrycode if outside USA

We will get back to you ASAP
-------------------------

Do Not Reply to this Email.
We do not reply to text inquiries, and our server will reject all response traffic.
We apologize for any inconvenience this may have caused you.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.