installing wicd does not uninstall networkmanager in lucid

[Bernhard]

Binary package hint: wicd

In current lucid beta 1, when I install wicd, it installs

1:05 % sudo aptitude install wicd
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
The following NEW packages will be installed:
  python-iniparse{a} python-wicd{a} wicd wicd-daemon{a} wicd-gtk{a}

but does not uninstall GNOME network manager. This can lead to problems when both deamons run at the same time. I recall that in older distros, GNOME network manager was automatically uninstalled when I install wicd.

[Richard Kleeman (kleeman)]

I can confirm this and the fact that having both daemons running was a problem. Why was the nm conflict dependency removed?

[izubaidi (izubaidi)]

I can confirm this

[gregrwm (gregrwm)]

iirc when i first installed lucid/lubuntu/wicd not long ago it was not available via ubuntu repos, i installed via ppa. now lubuntu is available via ubuntu repos. i confirm as of last week lubuntu-desktop via ubuntu repos *requires* network-manager, and adding wicd does not remove nm. i remove nm manually. then if i add ubuntu-desktop or edubuntu-desktop-kde nm is again required (and i remove it again). my problem now is that wicd starts seemingly too early and fails, syslog says "dhclient: Bind socket to interface: No such device", leaving me to start wicd manually, which does work. if i launch a desktop or wicd-curses first, wicd won't be running yet, and the client will require a password to launch it.

[jhansonxi (jhansonxi)]

I agree that the default configuration of wicd and Network Manager daemons conflict in Ubuntu 10.04 (Lucid Lynx). I don't agree that this is a package conflict. The two are not duplicates of functionality in one way - text mode interface.

Currently Ubuntu Recovery Mode has an option to run a package repair (the "dpkg" entry). It requires network access to be useful. The only network option is "netroot" which just runs dhclient. That is sufficient if you have a wired connection but it's useless with wireless. Network Manager doesn't have an equivalent to wicd-curses.

What is needed is a configuration option to run EITHER wicd OR network-manager daemons at specific runlevels. This means changes to the wicd init script and network-manager Upstart jobs, possibly needing Upstart profiles support.

[Marco Di Pietro (dptr-marco)]

I am on ubuntu 10.10 and i had the same conflict, wicd vs network-manager and my wifi card didn't connect to the ap while i was in text mode (gdm not started). I solved putting these lines in rc.local file:

/etc/init.d/networking stop
service network-manager stop
/etc/init.d/wicd start

then you could use wicd-client to setup your network if you haven't do it yet.
i

[Marco Di Pietro (dptr-marco)]

i forget to write that wicd was disabled in my runlevel (update-rc.d -f wicd remove). So it starts only after other network services go down.