wicd-client is being launched from the OP's session.

I agree with you (as you've mentioned in other posts) that you really should choose one way to manage your networks instead of a mix. Personally, I'll use /etc/rc.d/rc.inet1.conf to manage my networks on my desktops and /etc/rc.d/rc.networkmanager to manage my networks on my laptops.

I have used /etc/rc.d/rc.wireless.conf to manage wireless networks on laptops that I don't take out of my house, but that's a rare use-case for almost anyone.

If it's a laptop that needs to connect to god-knows-what-network, I'd advise the OP to use networkmanager instead of wicd, anyways.

Why ?
and
How ?

Well, you get networkmanager with no effort. It's part of the standard installation, versus going into /extras for wicd. There hasn't been much development on wicd lately (see https://code.launchpad.net/wicd), but that isn't necessarily a bad thing.

As for how, make /etc/rc.d/rc.networkmanager (IIRC since I'm not on one of my machines right now) executable and then run it via /etc/rc.d/rc.networkmanager start. It comes with applets for XFCE and KDE, so you can use a GUI to configure your network. There's a couple of not-graphical interfaces as well; nmcli (which is a command line tool) and nmtui (a curses based tool).

I used to use wicd myself and didn't find the switch to networkmanager to be difficult. If you've already done the work to get wicd up and running, you may as well continue to use it.

every time I try to run network manager
"/etc/rc.d/rc.wicd stop;/etc/rc.d/sh rc.networkmanager start"
then click on the icon in the panel
it bitches there is no network connection
WTF is just good for hard wired connections ?
do I have to configure it to use wlan0 or wlan1 ? (HOW ??)


this is how I ended up using wicd IT JUST WORKS !!
hard wired connections are easy all of the ethernet routers I have access to use dhcp so I just edit /etc/rc.d/rc.inet1.conf
in the eth0 section I enter "yes " to the question use dhcp
do an /etc/rc.d/rc.inet1 restart then download wicd pkg

You know I have used wicd and liked it. I also have used NetworkManager and liked it just as well. On this laptop, because of this thread I changed easily from wicd to NetworkManager and that is what I am using today. I wanted to see if it could be done as easily as I had assumed. NEVER have I had to edit , not once. This is for wifi and it was so easy to change and it is just as easy to change back.

My other computer is an old desktop with an ethernet connection and wicd. Why wicd? Just so I have an icon in the tray to hover over and see if I have a connection (rural living, many service problems). Wicd can be set for a default connection which it will satisfy first before going elsewhere. Example ethernet is default and if I had a wifi adapter on that machine then wifi would be miss congeniality. I made no edits to , none. It looks just like it does after a bare metal install.

Choose one method and make it work for you. Do one thing and do it well.
The truth is out there google it.
"site:linuxquestions.org wicd"
"site:linuxquestions.org networkmanager"
"site:linuxquestions.org rc.inet1.conf"

https://mirrors.slackware.com/slackw...ADME.SLACKWARE

I have one desktop wired and when setting up a new system on an SBC I will first set it up as wired. In both cases running slackware's netconfig I that's needed set up a connection. I've configure a netbook and two SBC's to connect wireless on the same network via wicd with fixed IPs

If you want to use wicd for a wired fixed IP make sure you have rc.d/networkmanager disabled and rc.d/rc.wicd enabled. You also should not have any entries in rc.inet.conf. Once you have wicd installed you can run wicd-client or in a terminal wicd-curses.

You only assign a single address in wicd to a machine with netconfig or wicd. Attached is an example configuration using wicd-curses.

So, the laptop that I'm using to write this normally uses networkmanager to connect via a wireless interface. I just took an Ethernet cable and plugged into a switch that is connected to my slackware64 gateway (which runs a DHCP server, among other things).

As far as I can tell, the machine saw the wired connection and started to use it with no effort on my part.

You're going to have to provide more detail for anyone to help you. OTOH, as I mentioned, if wicd is installed and working on your system, then I see no pressing reason to switch to networkmanager.

Sorry for not replying for a while. Will read the man pages and try to configure wicd. Thank you for your time.