That being the case, that this is really a Gnome programme and there is no real support for it in KDE, then it is definitely time that KDE developed it's own network manager. There is a lot of banging on about how KDE4.* it new, innovative etc etc, but the most fundamental thing, for laptop users anyway, is relegated to some sort of dodgy hack job almost as an afterthought. Consequently it doesn't work on many systems, and is annoying the bejesus out of a big segment of users. WICD is great for what it does, but it does have limitations, so in reality KDE does not have a fully functional, broad range network manager at all.

Legion wrote:That being the case, that this is really a Gnome programme and there is no real support for it in KDE, then it is definitely time that KDE developed it's own network manager. There is a lot of banging on about how KDE4.* it new, innovative etc etc, but the most fundamental thing, for laptop users anyway, is relegated to some sort of dodgy hack job almost as an afterthought. Consequently it doesn't work on many systems, and is annoying the bejesus out of a big segment of users. WICD is great for what it does, but it does have limitations, so in reality KDE does not have a fully functional, broad range network manager at all.

I'm sure that, if it were that easy, we wouldn't be having this discussion.

Madman wrote:

Legion wrote:That being the case, that this is really a Gnome programme and there is no real support for it in KDE, then it is definitely time that KDE developed it's own network manager. There is a lot of banging on about how KDE4.* it new, innovative etc etc, but the most fundamental thing, for laptop users anyway, is relegated to some sort of dodgy hack job almost as an afterthought. Consequently it doesn't work on many systems, and is annoying the bejesus out of a big segment of users. WICD is great for what it does, but it does have limitations, so in reality KDE does not have a fully functional, broad range network manager at all.

I'm sure that, if it were that easy, we wouldn't be having this discussion.

Maybe not, but the fact remains that we've been through KDE3 up to 5.10 with a network manager that worked well, and we are now up to kde4.3.1 without one. If network manager cannot be ported to kde4 then it is time to jettison it completely and find something that does work. I now use WICD, and am happy with it, but that not change the fact that, as I said, KDE does not have a fully functioning, broad range network manager.

Legion wrote:Maybe not, but the fact remains that we've been through KDE3 up to 5.10 with a network manager that worked well, and we are now up to kde4.3.1 without one. If network manager cannot be ported to kde4 then it is time to jettison it completely and find something that does work. I now use WICD, and am happy with it, but that not change the fact that, as I said, KDE does not have a fully functioning, broad range network manager.

Agreed. A proper Qt-based GUI for either of these services would be nice, but for some reason the developers of a desktop-agnostic service (NetworkManager) prefer one desktop over another (Gnome). It would be nicer if they developed the daemon and gave the developers of each desktop ample information to develop a front-end.

I have just spent the past hour bimbling through the WICD site, and it seems that planned for a V2 release is VPN/C, mobile networks and bluetooth, among other things. If they all come about then networkmanager has just lost the race, and deservedly so.

@Legion: that is excellent news. This makes Wicd far more capable, and will hopefully allow Network Manager to finally be displaced.

Legion wrote:I have just spent the past hour bimbling through the WICD site, and it seems that planned for a V2 release is VPN/C, mobile networks and bluetooth, among other things. If they all come about then networkmanager has just lost the race, and deservedly so.

All of a sudden, Wicd looks like it could replace NM for good...

Can someone please tell what process runs this net network manager, so I can kill it?

I need to run the nm-applet one by Gnome, because the KDE one does not allow one to connect to hidden wireless networks. But nm-applet will not run because when it trys to connect to DBUS the service is already consumed by the KDE one - and for the life of me I can not figure out what process owns this service or how to make it not run.

This was never a problem until I upgraded to the latest KDE. Previously I could exit this process via the system tray. Now, it seems all it does is hide the icon but it keeps running.

Run the following to disable KDE Network Management:

Code: Select all

qdbus org.kde.kded /kded unloadModule networkmanagement