• rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Topic: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

**NOTE** I just iinstalled Wicd 1.7.0 from the repos and it is working perfectly now. So no need to rollback as latest updates seem to have fixed things.

Just thought i'd post a quick message for those of you who may prefer Wicd over Network-Manager (I do).

I had wireless timeouts with nm-applet and network-manager so I removed it and installed Wicd 1.7 from the Squeeze repo.

I couldn't connect with WPA so I did a bit of Googling and apparently it's a common problem on other distros as well.

So I decided to roll back to Wicd 1.6.2.2 which is available from the Debian Lenny Backports repo:
http://packages.debian.org/search?suite … words=wicd

Once you have removed network-manager (obligatory as it conflicts with Wicd) you can download the .deb file and use Gdebi to install it. An apt-get - f install will also get any needed dependencies afterwards. For example: I had to reinstall wpasupplicant which was removed after the removal of network-manager.

I now have Wicd version 1.6.2.2 running perfectly with Wpa encryption and no timeouts or reconnects.

rich

Last edited by rich (2010-04-18 21:05:19)

| ultimate crunchbang howto everything | debianandi | g+ |
  • From: Ontario, Canada
  • Registered: 2009-06-29
  • Posts: 1,420

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

I might try that. Network-Manager had some problems with my wireless, i've been using Wicd 1.7 without any problems, except it sometimes has trouble connecting on boot, i have to cancel the connection and ask it to find networks and connect again. Perhaps 1.6.2.2 would fix this.

just call me...
~FSM~
  • rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

It seems you were lucky, I just kept getting the "bad password" error for 1.7.

Incidentally, just downloaded the 64bit Statler iso and have been browsing the web for an hour with no disconnects.

So for me, the 1.6 rollback appears to have worked.

Last edited by rich (2010-03-22 14:39:14)

| ultimate crunchbang howto everything | debianandi | g+ |
  • From: Ontario, Canada
  • Registered: 2009-06-29
  • Posts: 1,420

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

Perhaps it'd help to know if your using WPA or WPA2? I've been using WPA2.

just call me...
~FSM~
  • rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

blackbinary wrote:

Perhaps it'd help to know if your using WPA or WPA2? I've been using WPA2.

Wpa2, as we also spoke about here:
http://crunchbanglinux.org/forums/post/59728/#p59728

I did try with Wpa and Wpa2 but neither would connect.

Wicd ok now though.

| ultimate crunchbang howto everything | debianandi | g+ |
  • From: Ontario, Canada
  • Registered: 2009-06-29
  • Posts: 1,420

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

richs-lxh wrote:
blackbinary wrote:

Perhaps it'd help to know if your using WPA or WPA2? I've been using WPA2.

Wpa2, as we also spoke about here:
http://crunchbanglinux.org/forums/post/59728/#p59728

I did try with Wpa and Wpa2 but neither would connect.

Wicd ok now though.

Sorry, i didn't realize that thread was using wicd, thought it was network-manager.

just call me...
~FSM~
  • Erik
  • #! CrunchBanger
  • Offline
  • Registered: 2009-03-28
  • Posts: 162

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

Wow! That's the exact same problem I'm having! I haven't changed over to Statler, but this rollback may just work for me!

  • rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

blackbinary wrote:
richs-lxh wrote:
blackbinary wrote:

Perhaps it'd help to know if your using WPA or WPA2? I've been using WPA2.

Wpa2, as we also spoke about here:
http://crunchbanglinux.org/forums/post/59728/#p59728

I did try with Wpa and Wpa2 but neither would connect.

Wicd ok now though.

Sorry, i didn't realize that thread was using wicd, thought it was network-manager.

The wpa2 bit.

| ultimate crunchbang howto everything | debianandi | g+ |
  • rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

Just a quick note to say that I edited the first post as Wicd 1.7 from the repo is now working ok.

| ultimate crunchbang howto everything | debianandi | g+ |
  • Registered: 2009-02-09
  • Posts: 555

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

The only problem ive ever had with Wicd is it doest play well with my Sprint Mobil Broadband card.
Network Manager does this with ease.

  • rich
  • #! Junkie
  • Offline
  • From: teh interwebs
  • Registered: 2009-01-26
  • Posts: 408

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

Actually, Nm-Applet and Wicd are just gui frontends for ifconfig and wireless tools so it kind of also depends on your firmware. Although how the gui uses those backend tools is another thing.

I have Broadcom, Atheros, Cisco, Zydel and Ralink wireless cards, and each has proven to be good or bad depending on the distro and wirelkess firmware. However, I have had more success using Wicd than Network-Manager. Also it's a personal choice as I like to manually scan for essids and have direct access to settings and to be able to switch connections on and off at will. I find Wicd more accessible in this way.

| ultimate crunchbang howto everything | debianandi | g+ |
  • olembe
  • #! CrunchBanger
  • Offline
  • From: Salisbury, England
  • Registered: 2009-04-29
  • Posts: 247

Re: [Solved] Wicd 1.7 broken - Rollback to 1.6.2.2 needed for Wpa

I used to use wicd back when I ran Kubuntu (network-manager wouldn't work with that distro). A tip that saved me more than once was that I ALWAYS kept a .deb file of a known working  version of wicd on my hard disk, so I could reinstall it with dpkg if anything went wrong. In fact, I still have them on my hard disk even now!