[Bug 326105] Re: knetworkmanager doesn't start automatically

[Olaf Lenz]

It is true that knetworkmanager shouldn't start automatically anymore if
the system was upgraded to Jaunty, where the plasmoid is the default.

However, I think it should still be possible for a user to return to use
knetworkmanager in jaunty if the plasmoid doesn't work for him (or he
simply doesn't like it), no matter whether jaunty was installed from
scratch or via an upgrade from intrepid. At the moment, it looks as
though this is impossible, due to two or three bugs:

1. When trying to install network-manager-kde as long as plasma-widget-network-manager is installed, the following conflict during installation occurs:
E: /var/cache/apt/archives/network-manager-kde_1%3a0.7svn887517~2.19-0ubuntu1~ppa2_amd64.deb: trying to overwrite `/usr/share/kde4/services/kded/knetworkmanager.desktop', which is also in package plasma-widget-network-manager

I think that it should be possible to use both the knetworkmanager
applet and the plasmoid on a system, I don't see why there is this
conflict.

2. When first removing plasma-widget-network-manager, installing
network-manager-kde work fine. However knetworkmanager is still not
started automatically when logging out and in again, and no systray icon
appears.

3. I didn't find a way to start knetworkmanager manually either. There
is no "knetworkmanager" executable (as I believe was found in intrepid),
and neither modifying /etc/xdg/autostart/knetworkmanager-
autostart.desktop or ~/.kde/share/config/knetworkmanagerrc seemed to
result in anything.

So, I conclude, that at the moment, the package network-manager-kde is
completely useless in Jaunty, and should be either removed, or fixed.

** Changed in: knetworkmanager (Ubuntu)
       Status: Invalid => Confirmed

-- 
knetworkmanager doesn't start automatically
https://bugs.launchpad.net/bugs/326105
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to knetworkmanager in ubuntu.