knetworkmanager doesn't start automatically

[Romain1101]

Binary package hint: knetworkmanager

Description: Ubuntu jaunty (development branch)
Release: 9.04

Package: knetworkmanager
Versions:
1:0.7svn864988-0ubuntu8 (/var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_jaunty_main_binary-i386_Packages)
 Description Language:
                 File: /var/lib/apt/lists/fr.archive.ubuntu.com_ubuntu_dists_jaunty_main_binary-i386_Packages
                  MD5: a91fd9a6f46f6e81a8f37d473b159c7d

Reverse Depends:
  network-manager-kde,knetworkmanager
Dependencies:
1:0.7svn864988-0ubuntu8 - network-manager-kde (2 1:0.2ubuntu1-0ubuntu2)
Provides:
1:0.7svn864988-0ubuntu8 -
Reverse Provides:

Well usually KNM starts automatically with my system but since the last update of either KNM o KDE
I have to start it manually in order to have any good ifconfig config with IP registered in my WLAN
Besides, KNM doesn't appear either in the KDE menu or the krunner !!!
So I must start it with konsole !

ProblemType: Bug
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: knetworkmanager None [modified: /var/lib/dpkg/info/knetworkmanager.list]
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: knetworkmanager
Uname: Linux 2.6.28-5-generic i686

[Romain1101 (romainmadala)]

just a rectification [kind of error in my grub menu.lst]
uname gives actually :

Linux 2.6.28-6-generic i686

[Festr (festr2)]

I've the same issue. It is not starting automatically after upgrade some packages.

[Jonathan Thomas (echidnaman)]

It's not supposed to start automatically anymore. Instead, the new network management plasmoid has been added to the default Plasma setup. You may have to ad it manually if you were using Jaanty before that change.

[Madrid (enero)]

Johnathan Thomas: great joke, ha ha ha, great joke... Network managment plasmoid does not work (plasma-widget-network-manager). Why? Why? Why? WHY?! whhhhhhhhhhhhhyyyyyyyyyy? :-|

[Olaf Lenz (olenz)]

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.

[Olaf Lenz (olenz)]

I have just filed bug #362747, in which I summarize all the problems in connecting OpenVPN under Kubutnu jaunty.

[Brett Sheffield (brett-gladserv)]

Same problem. I upgraded last night from 8.10 -> 9.04 and part way through the upgrade networking stopped working.

After completing the upgrade I noticed Network manager had vanished from both the taskbar and the menus.

To get a DHCP address (wired) I had to either plug in the cable *after* booting had completed, or restart networking at the command line.

The knetworkmanager binary is still present, but even running it manually, it fails to start.

I've now added the network management widget and will start plugging my wpa keys back into that and testing wifi.

That's me sorted, but it's far from a smooth upgrade when networking vanishes with no explanation. Makes it hard for some to get online and find help.

Perhaps the networking widget should be installed by default? Yes, that's changing the user's desktop, but given that the upgrade process threw away my themes, desktop wallpaper and some other kde settings, this is a relatively small change :-)

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.