Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


View Poll Results: wicd or networkmanager?
wicd 70 49.65%
networkmanager 79 56.03%
Multiple Choice Poll. Voters: 141. You may not vote on this poll

  Search this Thread
Old 04-20-2013, 09:06 AM   #16
Senior Member
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib." FreeBSD.
Posts: 2,493

Rep: Reputation: 275Reputation: 275Reputation: 275

I've used both and if wicd it didn't have a 'refresh' button it would be completely worthless. NM, on the other hand, seems to do a better job of making the connection and hanging on to it.
Old 04-20-2013, 09:41 AM   #17
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,647

Rep: Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745Reputation: 745
I've used both. I'm using wicd on my slackware-current acer netbook. I prefer wicd; it does what I need it to do.
Old 04-20-2013, 10:16 AM   #18
Senior Member
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 3,990

Rep: Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100Reputation: 1100
For my comparison of NetworkManager and wicd, see here
Due to USB modem support and automatic reconnection, I am using NetworkManager in preference to wicd on my netbook.
1 members found this post helpful.
Old 04-20-2013, 10:39 AM   #19
Registered: Aug 2009
Location: /Universe/Earth/India/Pune
Distribution: Slackware64 -Current, Linux Mint 17.1
Posts: 821

Rep: Reputation: 128Reputation: 128
I use both. Network-manager for personal 3G USB dongle and wicd for the wi-fi.

Old 04-20-2013, 10:46 AM   #20
Senior Member
Registered: May 2004
Location: Belgium
Distribution: Debian, Slackware, Fedora
Posts: 1,262

Rep: Reputation: 189Reputation: 189
Originally Posted by onebuck View Post

I use 'wicd' via 'wicd-curses' when on console'cli'
Didn't know it had ncurses interface.

I mostly use NM since Wicd doesn't support everything in my home network.

Last edited by jens; 04-20-2013 at 10:48 AM.
Old 04-20-2013, 11:57 AM   #21
Didier Spaier
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad W520
Posts: 5,639

Rep: Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587Reputation: 1587
Now that netconfig proposes NetworkManager, I use it (on my laptop, with Fluxbox.)

At first reboot after installation:
(1) I am automatically connected by wire, if available
(2) I just have just to run once nm-applet to get the widget on the tray after installation.

Then getting a wireless connection is just a left-click away, plus possibly typing the password the first time when demanded.

It could hardly be simpler to use IMO.
Old 04-20-2013, 03:03 PM   #22
Registered: Oct 2003
Location: WA
Distribution: Slackware64 14.1, Slackware 14.1
Posts: 599

Rep: Reputation: 160Reputation: 160

Maybe its just my weird old laptops (Compaq and Dell), but NM has one hell of a time switching back to wired from wireless; wired TO wireless is fine, but the reverse requires more button clicks than I care for. For systems without wifi, I disable NM: easier to just edit the appropriate files in /etc/rc.d
Old 04-20-2013, 03:18 PM   #23
Registered: Jan 2011
Location: Czech Republic
Distribution: Slackware, Gentoo, FreeBSD
Posts: 160

Rep: Reputation: 21
I use both. Each has it's own glitches, but I get used to "wicd way" so now I find NetworkManager's applet the weird one Although I'm pretty sure anyone coming from NetworkManager to Wicd will feel the same about wicd.

I use networkmanager for VPN and wicd for everything else.

So far wicd always worked flawless, while networkmanager sometimes acts weird (can connect to wired network but didn't even try to connect to wireless network, although it connected fine just few minutes ago). Besides, wicd doesn't intentionally hide informations (like complete list of available wifi AP's, so I can choose AP if it operates on both 2.4 GHz and 5 GHz band) to simplify GUI. Which I find as advantage, but someone else could take it as disadvantage. It's matter of preferences.

Last edited by yenn; 04-20-2013 at 03:20 PM.
Old 04-21-2013, 09:38 AM   #24
Registered: Jun 2012
Posts: 78

Rep: Reputation: Disabled
Neither. Wired eth0 here.
Old 04-21-2013, 09:18 PM   #25
Registered: Feb 2013
Location: Sydney
Distribution: slackware
Posts: 108

Rep: Reputation: 36
At one point (maybe fixed now?) wicd had a bug that meant automatic wifi reconnections sometimes didn't work (maybe after reawakening from hibernation?). I remember I had to actually restart for the connection to be accepted with the stored credentials.

Since NetworkManager appeared I have used it for my laptop and this problem has not occurred.

Old 04-21-2013, 09:27 PM   #26
Timothy Miller
Senior Member
Registered: Feb 2003
Location: Arizona, USA
Distribution: Debian Stretch, Netrunner rolling, Mageia...
Posts: 1,050

Rep: Reputation: 190Reputation: 190
I can't get NM to connect automatically on boot if X isn't running, so it's no choice for me, Wicd.
Old 04-22-2013, 01:10 AM   #27
Registered: May 2004
Distribution: Slackware
Posts: 46

Rep: Reputation: 23
I use wicd, with the dhcpcd backend. The dhclient backend changes my computer's hostname without my permission, which (aside from being rude) wreaks havoc on the desktop session.

I like that Wicd gives me more options and easier access to configuration. The interface is a little sluggish (it likes to refresh a lot?), but I find it works better for me than NM. NM didn't always play nicely with a multi-user setup and kept forgetting passwords in a way that made no sense to me. Wicd works fine, so long as I don't use the dhclient backend :P

Last edited by josiah; 04-22-2013 at 01:11 AM.
Old 04-22-2013, 08:11 AM   #28
Senior Member
Registered: Dec 2008
Posts: 1,014

Rep: Reputation: 147Reputation: 147
Originally Posted by vdemuth View Post
I use both depending on circumstances. Mostly to do with 3G dongles being recognised and usable with NM. But on the whole, it seems that Wicd is just more stable and reliable.

A PITA having to swap about, so the sooner Wicd gets 3G support the sooner I can ditch Nm.
I switched to NetworkManager for the same reason but soon found NetworkManager forces me to accept too many things. e.g. It forces me to let it manager my ethX while in wicd I can disable this. NetworkManager also disallows the use of "/etc/resolv.conf.{head,tail}".

After quite some struggles, I had to switch back to wicd+blueman. Blueman also gives more stable 3G modem connection than NetworkNamager does.
Old 04-30-2013, 09:28 PM   #29
Registered: Sep 2009
Location: Perth, W.A.
Distribution: Slackware 14, Debian 8, FreeBSD 10, OpenBSD
Posts: 189

Rep: Reputation: 35
I dislike both of them because of bloat, so I use wpa_supplicant and hand edit its config as needed.

If I had to choose, it would be wicd, but I very much dislike its design decisions. I mean, c'mon, it expects me to run a full Python interpreter as a daemon? Along with a bunch of third-party libraries. And as root? WT...?

It's been on my To-do list for ages: write a simple wireless manager in C that would interface with iwlist and iwconfig or iw to bring up and close down wireless connections. It would automatically remember certain APs and would offer to connect when one comes in range, all user configurable.

I think it is something that is really lacking in Slackware land at the moment, especially for those of us who don't use a Desktop and have no concept of a systray or applets.
1 members found this post helpful.
Old 05-01-2013, 12:11 AM   #30
Senior Member
Registered: Sep 2004
Distribution: slackware
Posts: 1,839

Rep: Reputation: 276Reputation: 276Reputation: 276
Originally Posted by joncr View Post
Neither. Wired eth0 here.
Yessirree! Same on the desktop.

On the laptop, however, I use NetworkManager because it is the default in KDE and works very well out of the box. It has been a solid performer for me.

It wasn't that long ago that the kernel didn't have many wireless drivers built in. I had a wireless card which used an Atheros chipset. Had to download the Madwifi drivers and compile them, as well as wpa_supplicant which wasn't a stock Slackware package. Things have certainly come a long way since 2004!


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
What is the advantage (if any) of NetworkManager over wicd? BobNutfield Slackware 28 07-13-2012 06:24 AM
[SOLVED] NetworkManager lopid Slackware 8 05-13-2012 12:22 PM
NetworkManager dbswifty Linux - Newbie 6 08-23-2010 05:05 PM
networkmanager giraf Ubuntu 7 05-05-2010 04:22 PM
WICD tray icon says not connected, WICD manager says conneted to wired network?!?! intheshadows Linux - Newbie 1 12-24-2009 12:15 PM

All times are GMT -5. The time now is 08:37 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration