You are not logged in.
I got tired of the default network manager lagging on me, etc so I installed Wicd from the repo....it will remove nm automatically.
edit autostart.sh and replace "nm-applet" with "wicd-py" so the wicd applet will show up in your tray at boot up.
I searched and didn't see anything on this so thought I should add to the database.
EDIT: forgot, works much better! (usually does IM experience
)
Last edited by theZoid (2009-07-16 01:38:51)
Cheers, Big Ears!
DΞLL Precision M6500 "Big Dog": i7-820QM w/USB 3.0, 8.0GB DDR3-1333, Intel x-25M 160 G2 + 500GB 7200.3, nVidia Quadro FX 3800M 1.0GB DDR3, RGBLED, Intel 6300 //Win7Pro x64/Sabayon KDE 4.5.4 x64
Offline
I'm certain that it's somewhere here on the forums, but no matter. And all I have to do is manually start wicd-client after installing wicd and then I get the icon in my tray regardless of whether you add it to autostart.sh or not. Doesn't need to be added.
Offline
wicd is discussed in several threads here. Some people need to run wicd-client in their autostart to get the tray icon, others not.
I've been a big advocate of wicd to be included as the default in crunchbang but I must say that nm in 9.04.01 is very good and I've seen no need to change to wicd as yet.
Offline
I've been a big advocate of wicd to be included as the default in crunchbang but I must say that nm in 9.04.01 is very good and I've seen no need to change to wicd as yet.
I have had cause to use wicd on occasion and I like it, the only feature it lacks for me is the USB modem support. Once this is included, I think we should reconsider its inclusion.
Ex-developer of #! CrunchBang. Follow me on Twitter 
Offline
I'm certain that it's somewhere here on the forums, but no matter. And all I have to do is manually start wicd-client after installing wicd and then I get the icon in my tray regardless of whether you add it to autostart.sh or not. Doesn't need to be added.
OK thanks....same with Slackware, but with OpenBox I didn't try it any other way...
Cheers, Big Ears!
DΞLL Precision M6500 "Big Dog": i7-820QM w/USB 3.0, 8.0GB DDR3-1333, Intel x-25M 160 G2 + 500GB 7200.3, nVidia Quadro FX 3800M 1.0GB DDR3, RGBLED, Intel 6300 //Win7Pro x64/Sabayon KDE 4.5.4 x64
Offline
Since I'm using a laptop, I've just found it more convenient to use wicd so that my internet is connected when I login. I run mail-notification, xfce4-weather-plugin, and so forth, and I hate having to update the tray icons. I know there are other ways of having a wireless connection with nm-applet at login, but for me, wicd is just hasslefree.
That being said, I agree that nm-applet is wonderful, and honestly, tends to work better for me in general (gives more accurate signal strength readings... wicd-client reports 100+ percent often -- some report the opposite to be true in favor of wicd on this point), but still, it's ease of use that's won me over.
At any rate, I'm happy using either. I remember the early days of Ubuntu, linux in general, and what PITA connecting wirelessly was. Linux has definitely come a long way 
Last edited by RubiksQubed (2009-07-16 04:43:51)
Offline
Some people need to run wicd-client in their autostart to get the tray icon, others not..
with #! 8.10/8.04 you have to run wicd-client and add wicd-client to autostart.sh
it isn't needed anymore - if you run #! 9.04
with command line, you can run wicd-client -n to open wicd gui
Offline
with #! 8.10/8.04 you have to run wicd-client and add wicd-client to autostart.sh
I didn't have to do that with 8.10
Offline
klanger wrote:with #! 8.10/8.04 you have to run wicd-client and add wicd-client to autostart.sh
I didn't have to do that with 8.10
Hmm, so it seems, that it is hardware not software related 
On eeepc (900) with #! 8.10 I had to add to autostart.sh wicd-client.
Now with 9.04 it wasn't nessesery.
Anyway, if you don't have a wicd icon in tray, add wicd-client to autostart.sh + disable nm-applet (network manager in autostart.sh) and/or run wicd-client (-n to start gui)
Last edited by klanger (2009-07-16 06:50:10)
Offline
Weird as it may sound, but recently my dsl line is faulty and needed to connect to my bro's across the street.
My Debian setup using nm-applet is unable to connect as the signal is detected as weak.
Dual-booting into another setup using wicd, I am able to connect as wicd reported the signal as acceptable.
Out of curiosity, I went over to my bro's place to connect and replace nm-applet with wicd.
Went back home and confirmed that my Debian setup is now able to connect to his signal - wicd reported that the signal is acceptable.
Now, I have switched all my laptop/desktop/netbook from nm-applet to wicd
Hope this info is useful to some 
Offline
I am also in favor of wicd by default in #!.
I like network manager since I figured out how to connect without having to enter my password every time, but for some reason it would sit in the tray and wait ~ 30 secs before connecting on #!.
Wicd connects after a few secs, and, since I'm using #! for the amazing quickness, this completes me.
Statler-Openbox on an Acer Extensa 4420. Its good to be back.
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.