Upgrade from Karmic to Lucid installs BOTH wicd and knetworkmanager

Bug #559386 reported by a_h_roth@yahoo.com on 2010-04-09
This bug affects 2 people
Affects Status Importance Assigned to Milestone
wicd (Ubuntu)

Bug Description

Binary package hint: wicd


When upgrading for a Kubuntu Karmic installation with Wicd (and no knetworkmanager) to Lucid, Wicd isn't handled properly. In the resulting Lucid installation, BOTH wicd and knetworkmanager are installed. This causes the WiFi connection to go in and out, without settling on a strong connection.

SUGGESTED BEHAVIOR: is that the upgrade detects Wicd and does NOT install knetworkmanager in the first place.
ALTERNATIVE: the upgrade detects wicd, uninstalls it, and installs knetwork manager.

Uninstalling wicd allows me to use knetworkmanager with no problems. I haven't gotten around to replacing knetworkmanager with wicd, so I don't know for a fact that uninstalling knetworkmanager and leaving wicd would work.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: wicd (not installed)
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic-pae
Uname: Linux 2.6.32-19-generic-pae i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Fri Apr 9 12:22:56 2010
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
SourcePackage: wicd

summary: - Upgrade from Karma to Lucid installs BOTH wicd and knetworkmanager
+ Upgrade from Karmic to Lucid installs BOTH wicd and knetworkmanager
Danny (d-engelbarts) wrote :

I experienced the same problem upgrading from Lucid to Maverick. I prefer wicd to networkmanager, partly because it allows me to get wireless access on some networks where network-manager does not. After the upgrade to Maverick i could not access my wireless network, a quick check showed network-manager was installed and started. After disabling and purging network-manager wicd works as it used to.

I chose to use wicd instead of network-manager, i believe the upgrade should not install network-manager, especially when wicd is installed as well. It should respect my previous choices and only change to network-manager if wicd was not not supported in the upgraded environment.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers