Version: (using KDE 4.4.1) Installed from: Ubuntu Packages When system disable networking and because of bug (example: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/533471 ) or other reasons not enable it automaticly, KDE user can't find easy way to enable networking. 1. KNetworkManager not have enable/disable networking checkbox. 2. Even if KNetworkManager have this checkbox - there is no way to access to KNetworkManager if networking diabled. 3. Only GUI-way, what I found, it's enable/disable networking using network management plasmoid, but it's bad way, you know.
I can confirm this behavior on Debian Squeeze: network-manager-kde Version: 1:0.9~svn1088283-1 network-manager Version: 0.8-1 knm-runtime Version: 0.1~svn1088283-1 I believe the severity of this bug should be upgraded to "MAJOR" as it can render the application completely useless.
Maybe change logic of KNetworkManager? Allow user to launch it even networking disabled, and provide checkbox or button "Enable networking" in popup menu.
*** This bug has been confirmed by popular vote. ***
i have the same issue (kde 4.4.2) knetworkmanager 0.9 svn1088283-1 i had to open (gnome's) nm-applet . select the "enable" checkbox. close it. and start knetworkmanager for it to work. ( i was getting "network management disabled" before )
*** Bug 235477 has been marked as a duplicate of this bug. ***
same problem here in kubuntu lucid. If a system freeze or crash occurs, networkmanager leaves network disabled and there is no user friendly way to reenable it in knetworkmanager. Should be hig priority fixed for me too.
This problem persists in KDE 4.5rc1. Knetworkmanager is useless in this situation as it only reports "networking disabled" and offers no way to fix it. The only course of action is to kill knetworkmanager, manually edit/var/lib/NetworkManager NetworkManager.state to set NetworkingEnabled=true and restart network-manager and knetworkmanager. This has gone on long enough and needs to be addressed. There is no reason knetworkmanger cannot handle this situation this far into the 4.x version. This should be an easy fix and needs to be incorporated into 4.5 before the freeze.
This is the second time this problem is happening to me. Most probably it's the distro's fault, because somehow, this flag is changed on an upgrade. Point is, when it show the "Network Management disabled" also should show an option to enable it. Very few users would know how to solve this problem...worse is, without being able to reach the network.
Same problem here with kde 4.5 rc2.
In Kubuntu Maverick this problem solved by replace KNetworkManager to Network Manager Plasmoid.
Same problem on Kubuntu 10.04 Lucid Lynx: sometimes on system resume after suspend I got networking disabled and I have to killall knetworkmanager and start nm-appet from gnome just to tick the enable networking switch. To remove this bug it could be sufficient to add this simple function to knetworkmanager too.
Created attachment 51612 [details] SYSLOG of the deactivated Network-WLAN-connection
(In reply to comment #11) > Same problem on Kubuntu 10.04 Lucid Lynx: sometimes on system resume after > suspend I got networking disabled and I have to killall knetworkmanager and > start nm-appet from gnome just to tick the enable networking switch. I've got the same problem under KDE4.4.2 But the NetworkManager reports 'unmanaged' instead of 'unavailable' I append the SYSLOG at that situation below.
NetworkManager daemon now uses two states to disable networking: sleep/wake - this is just for suspend/resume cases and is just available for root by default enable/disable - this is meant for user interaction and this state is what nm-applet's "Enable Networking" controls kde plasma applet is now also patched to use enable/disable. As far as monolithic knetworkmanager is concerned, the patch for adding "Enable Networking" checkbox is present in bug 238325. It has been included in Fedora. However, you have to prod upstream to accept it as well, or request your distro maintainers (seems that there aren't much interest in knetworkmanager because it's deprecated by the plasmoid). As for resume failures, there's usually the problem that NM daemon is not correctly awaken. Run this as root to wake it up: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Sleep boolean:false To simulate "Enable Networking" use: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.Enable boolean:true
This issue appears to be a duplicate of Bug 223030.
let's consolodate on bug #238325 , that implementation has been accepted and imported already. *** This bug has been marked as a duplicate of bug 238325 ***