Bug 223030 - Knetworkmanager can not "able networking"
Summary: Knetworkmanager can not "able networking"
Status: RESOLVED DUPLICATE of bug 238325
Alias: None
Product: knetworkmanager
Classification: Miscellaneous
Component: general (show other bugs)
Version: 0.9
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Will Stephenson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-16 21:12 UTC by Atle Olsson
Modified: 2010-10-25 16:00 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Atle Olsson 2010-01-16 21:12:01 UTC
Version:           0.9 (using KDE 4.3.4)
OS:                Linux
Installed from:    Fedora RPMs

Upon somehow manage to disable networking with the knetworkmanager, knetworkmanager is 100% disabled. It got no of enabling "networking", and a result it will display the message: "Network Manager Disabled".
The only way to enable it is:
1. Enable networkmanager networking in some config file, which I do not know if it exists
2. Installing gnomes network manager, and enabeling it from there...... then removing it and then enabling KDE's...........

How to reproduce:
Find the config file and disable networking, OR: Using gnomes network manager to disable networking
Comment 1 JR 2010-02-12 06:08:49 UTC
I ended up getting this. Unsure as to what could have disabled networking in NetworkManager, but something did. This is on a Kubuntu 10.04 Lucid machine, running KDE 4.4. knetworkmanager version 1:0.9~svn1075616-0ubuntu1.

Upon logging in a few days ago, the KNetworkManager context menu just had a greyed out entry saying "Network Management is disabled", and mouseovering the tray icon spawned a pop up saying "Unmanaged".

Much as the reporter mentions, the solution I finally found (a few days later) was to install GNOME's nm-applet, start it, right click its tray icon and hit "Enable networking". I just had to get networking to work first in order to download it, which put me in a catch 22 (needed networking to enable networking).

There really should be an equavilent menu option in KNetworkManager, or at least in the System Settings KCM module.

How to reproduce (skip steps 1-4 if you or [eg] an update script manually disabled networking in NetworkManager):
1. Install nm-applet (network-manager-gnome in ubuntu repos)
2. killall knetworkmanager
3. Start nm-applet, disable networking
4. killall nm-applet, uninstall it, clean package archive
5. Start knetworkmanager
6. Sticky situation!
Comment 2 ned 2010-02-13 12:46:10 UTC
Agree, a disable/enable networking option à la gnome nm-applet is a vital feature, especially since knetworkmanager in Ubuntu Lucid doesn't appear to automatically enable NetworkManager...
Comment 3 Bartosz Brachaczek 2010-03-01 19:30:29 UTC
I can confirm that lack of this feature can be very problematic, especially when someone hits this bug: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/291062 (it's not Ubuntu specific, I've hit it on Gentoo using NetworkManager-0.7.2).
Comment 4 Rex Dieter 2010-03-08 15:18:39 UTC
confirmed.
Comment 5 Bartosz Brachaczek 2010-03-12 17:29:41 UTC
Probably the main problem is that currently KDE doesn't recognize ASLEEP State for NetworkManager (Solid::Control::NetworkManager::status() returns Solid::Networking::Unknown - Solid::Networking::Asleep should be defined and recognized properly). Or I'm wrong and it is recognized in a different way.

Second thing is that a proper "Enable networking" checkbox should (or not?) be added to the tray icon's popup menu. I see there is already something like that in the NMPopup code for Plasma (I don't know if it works as the applet crashes plasma immediately after adding it).

As a workaround, we could just enable networking* unconditionally somewhere where it'd be able to be called not only at startup (I did it in KNetworkManagerTrayIcon::fillPopup() and this 1 additional line of code solved the problem for me).

* by calling Solid::Control::NetworkManager::setNetworkingEnabled(true);
Comment 6 Rex Dieter 2010-06-11 18:19:41 UTC
See one possible implementation (with patches) in bug #238325
Comment 7 Tristan Miller 2010-10-25 14:32:59 UTC
This issue appears to be a duplicate of Bug 232531.
Comment 8 Rex Dieter 2010-10-25 16:00:11 UTC
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 ***