You are not logged in.
Pages: 1
Topic closed
I'm looking at giving #! a test-run on my laptop later today and I'm wondering if it has any packages that depend on on NetworkManager? I much prefer Wicd to NM, and want to make sure I'm not going to cause any major breakage when I remove NetworkManager.
Anyone else done this? Any issues giving NetworkManager the boot?
I intend to get wicd from
deb http://apt.wicd.net intrepid extrasunless #! actually provides it.
Offline
if you install Wicd (it's in the repo's already, you don't need to add any) then it will automagically remove nm.
Remember: you still need to edit autostart.sh to make wicd start on log-in
Ex-KDE user.
Collects old PC's (Coz he can't afford new ones =P)
Crunchbang @ Distrowatch
My Blog (updated infrequently, and on the #! Planet too.)
Offline
CrunchBang does include wicd in its repository though the wicd repository is slightly newer.
Note: ** Please read before posting **
BTW if you wish to contact me, send me an e-mail instead of a PM.
Online
Having experienced some wireless network bad voodoo using NM and a DLink G-122 USB dongle wireless adapter under NM, I decided I give wicd a spin to see if it could do any better. Unfortunately now I get zero activity from my adapter, no green flickering lights or nothing, any idea what went wrong there?
Offline
unless #! actually provides it.
sudo apt-get update && sudo apt-get install wicdOffline
Remember: you still need to edit autostart.sh to make wicd start on log-in
You don't have to do this any more. The wicd daemon is started during the boot process and will appear in your systray after log-in. This gives a quicker wireless connection and is another reason I like in better than nm. 
Offline
Mehall wrote:Remember: you still need to edit autostart.sh to make wicd start on log-in
You don't have to do this any more. The wicd daemon is started during the boot process and will appear in your systray after log-in.
but the wicd icon isn't up in the tray - you have to (in terminal) type wicd-client to open up the icon.
if you enable the wicd script in autostart.sh the icon will be open after the login
(in cruncheee)
Offline
but the wicd icon isn't up in the tray - you have to (in terminal) type wicd-client to open up the icon.
if you enable the wicd script in autostart.sh the icon will be open after the login
Strange, it just starts and appears in the systray for me without having to add anything to autostart.sh. Perhaps it's because I have auto-connects configured. I'm not sure.
Offline
Does wicd allow the use of broadband cards?
Offline
I installed wicd and it did not see my sprint broadband card like network-manager, so I went back.
Offline
I've installed wicd on my Eee 701 and I haven't gotten wireless to work so far. Currently configured to ath0, which should be correct. I have this sneaking suspicion it is an easy fix
Offline
klanger wrote:but the wicd icon isn't up in the tray - you have to (in terminal) type wicd-client to open up the icon.
if you enable the wicd script in autostart.sh the icon will be open after the login
Strange, it just starts and appears in the systray for me without having to add anything to autostart.sh. Perhaps it's because I have auto-connects configured. I'm not sure.
This is because of lxsession when I switched to #! but kept my old autostart.sh, I suddenly had two instances of WICD. Funny thing.
I'm so meta, even this acronym
Offline
I've installed wicd on my Eee 701 and I haven't gotten wireless to work so far. Currently configured to ath0, which should be correct. I have this sneaking suspicion it is an easy fix
I'm still not sure why I can't get it to work. Do I have to mess with my wireless driver?
Offline
Strange, it just starts and appears in the systray for me without having to add anything to autostart.sh. Perhaps it's because I have auto-connects configured. I'm not sure.
I guess it is because of lxsession. When i added wicd-client and eee-control-tray in autostart.sh, i had two icons of each in tray. As a non-networking application is involved, i guess it is lxsession, not auto-connect.
Wicd rocks, by the way. )
Offline
Yes I think Crunchbang should replace nm-applet with wicd....it is alot better! I just changed and no problems anymore like I had with NM-applet that took 30sec-1 min to connect...wicd is connected after 1 sec.
Offline
Installed through wicd repos and everything worked great, those not intending to use a 3g modem should change to wicd without thinking twice.

Last edited by twinned (2009-10-29 06:25:54)
Offline
Hi all. I'm messing with wicd 1.5.9 again and once again having problems, but things are going better than before on my Eee 701 4g w/#! 9.04
Here is the link. The first time I ran wicd after reboot wireless network did show up with "wlan0" and "wext" but I was unable to connect the local WEP connection. I'm not sure whether the problem is encryption related (I installed WPAsupplicant), wext related (is it the best choice?) or maybe even wlan0 related (I have an atheros wireless card installed). Thoughts or ideas greatly appreciated.
Should I try using the more recent 1.7 release of wicd?
Offline
In my experience, I had only to disable the service network-manager (I dont remember exactly the name) through sysv-rc-conf, because I didnt uninstalled nm-applet package.
Offline
I've seen that installing wicd removes networkmanager, but does it do so in statler?
A world without what makes us, us. One without you or me.
A world with no differences, this is the world I see.
Offline
Don't think so...
Just installed wcid, and nm is still hanging around, and so I'm getting no connectivity on WCID, I think you have to uninstall manually...
It turns out that when I decide to live dangerously, I choose the red slushie instead of the blue one... HUGE. MISTAKE.
Offline
installing WICD will not automatically remove network-manager. I just installed wicd and had to manually (not really but through the synaptic) network-manager. so far working far better than the NM.
btw this is on a lenovo t60 laptop. don't know what the card it but working with minor things not happening such as icon in xfce4 panel. but can easily change that i believe.
EDIT: wicd automatically added itself to the autostart.sh from what i am seeing.
Last edited by cobaltwolfe (2011-08-24 01:56:10)
"Alles brennt wenn die Flamme ist heiß genug, die Welt ist nichts aber ein tiegel"
Offline
installing WICD will not automatically remove network-manager. I just installed wicd and had to manually (not really but through the synaptic) network-manager. so far working far better than the NM.
I second this.
Now lets reboot and make sure it all works automagically.
Statler-Openbox on an Acer Extensa 4420. Its good to be back.
Offline
installing WICD will not automatically remove network-manager. I just installed wicd and had to manually (not really but through the synaptic) network-manager. so far working far better than the NM.
btw this is on a lenovo t60 laptop. don't know what the card it but working with minor things not happening such as icon in xfce4 panel. but can easily change that i believe.
EDIT: wicd automatically added itself to the autostart.sh from what i am seeing.
What are the advantages of WICD over NM?
#! 10 “Statler” r20110207 32-bit & Openbox
Offline
@cobaltwolfe - Please don't bump such old help threads. Its more than 1 year since the last reply and more than 2 years since it was created.
/closed
Note: ** Please read before posting **
BTW if you wish to contact me, send me an e-mail instead of a PM.
Online
Pages: 1
Topic closed
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.