Hello everybody,

First of all, let me say I have absolutely nothing against knetworkmanager (btw, where did the knetworkmanager binary go with the upgrade to 4.6? =/). I think it's great (haven't tried it yet with mobile broadband, but hope it will work if I plug a 3G USB modem), and really like the new interface.

Unfortunately, knetworkmanager never seems to work with my tethered wifi through my Android phone (Motorola Droid 1). It did not work on 4.4 and now that I made the upgrade to 4.6.2 it does not work either. This wouldn't be a problem since on 4.4 I used to just kill knetworkmanager and start nm-applet, which did connect to the tethered wifi (strangely enough, for a 3G USB modem it is the other way around, nm-applet can't and knetworkmanager can). However, I can't start nm-applet under KDE-4.6.2. I can remove the network manager applet from the system tray, but whenever I try to start nm-applet it says that an instance is already running.

I tested under fluxbox and was able to start nm-applet successfully, so what am I missing? Since there is no knetworkmanager binary running, how can I "stop" it so I can start nm-applet? Surely the solution would not be kill Plasma and do without it right?

Thanks in advance.

Cheers,
GODLiKE.-

GODLiKE wrote:First of all, let me say I have absolutely nothing against knetworkmanager (btw, where did the knetworkmanager binary go with the upgrade to 4.6? =/).

It's been deprecated in favor of the plasmoid (called NetworkManagement).

can). However, I can't start nm-applet under KDE-4.6.2. I can remove the network manager applet from the system tray, but whenever I try to start nm-applet it says that an instance is already running.

In order to decouple network handling from Plasma (as that would mean losing network if it crashes), NM is handled through a special module (networkmanagement) by the KDE Daemon (KDED).

You can try disabling it entirely by typing in a terminal

Code: Select all

qdbus org.kde.kded /kded unloadModule networkmanagement

This should solve the issue you are facing.

Thanks einar, I'll be sure to try it out.

Just a question: will "loadModule" instead of "unloadModule" work the other way around? In case I wish to switch back to knetworkmanager of course.

EDIT: I tested and it works I don't have to kill anything nor remove the plasmoid. which is great. Thanks!

Yes, changing "unloadModule" to "loadModule" will cause it to load up again and return to service. Make sure that nm-applet is closed when you do that.

Do note that you need to run unloadModule on each startup, but can put it into a script in ~/.config/autostart/ to have it run on startup.

I made the following simple script in order to manage this, since it's more the number of times I want to use KNetworkmanager than the number of times I need to user nm-applet:

Code: Select all

#!/bin/bash

if [ "$1" == 1 ]
then
    qdbus org.kde.kded /kded unloadModule networkmanagement
elif [ "$1" == 2 ]
then
    qdbus org.kde.kded /kded loadModule networkmanagement
fi

I could add a `kill -9 $NM_APPLET_PID` on the second part of the if... good idea .

Thanks again. Hope this is useful for anybody else since I could not find any docs on this.

I have similar problems. I haven't been able to connect to WPA Enterprise wifi (university) using knetworkmanager or the new plasmoid, while nm-applet is able to connect to WPA Enterprise. Thanks for posting a solution, the script is very useful. In the meanwhile I have figured out a gui way of allowing nm-applet to run:

In Startup and Shutdown module of System Settings (KDE control center):
- Disable and stop "Network Status" and "Network User settings" services
- Add a new startup program with path /usr/bin/nm-applet (could be different on other systems)
- logout and log in again.

I'd be interested in knowing if this works (doesn't work)