[SOLVED] Wicd not accepting wifi configuration - Slackware64 -current

spudgunner · 05-03-2012, 08:48 PM

I've just done a fresh install of Slackware64 -current and installed wicd. When I click properties below any network, the 'ok' and 'cancel' buttons don't work, and exiting the window doesn't save my configuration. Amy suggestions on what to try?

slackass · 05-03-2012, 11:05 PM

wicd has been giving me fits.
I can't get it to work on any of my boxes since the upgrade.(13.37 & current)
I tried kde network manager on one box but it choked back some how.
I could nav a site but could not download anything.
Going to do a fresh install and play with wicd to see what I can figure out.

markush · 05-04-2012, 12:28 AM

Hi,

I've once tried wicd, it never worked for me. You don't need it.

For the wireless connection with my laptop I've created my own startupscript

Code:

#!/bin/sh
ifconfig lo up
ifconfig wlan0 up
wpa_supplicant -iwlan0 -Dwext -c/etc/wpa_supplicant.conf &
dhcpcd wlan0

It is started from rc.local. I've disabled the rc.inet1 script.

If I want (seldom) to start eth0, I execute "ifconfig eth0" and "dhcpcd eth0" manually as root.

Markus

slackass · 05-04-2012, 12:38 AM

Thanks Markus!
I'll mess around with it.

spudgunner · 05-04-2012, 07:26 AM

Quote:

Originally Posted by slackass

wicd has been giving me fits.
I can't get it to work on any of my boxes since the upgrade.(13.37 & current)
I tried kde network manager on one box but it choked back some how.
I could nav a site but could not download anything.
Going to do a fresh install and play with wicd to see what I can figure out.

I was having problems as well before my fresh install and I couldn't figure it out, so that's why I did the fresh install.

@markush: Thanks for the advice, I'm well aware of doing it that way, but it's on a laptop I don't want to be editing wpa_supplicant.conf every time I switch APs.

gapan · 05-04-2012, 08:31 AM

It is a bug with wicd 1.7.2.4: https://bugs.launchpad.net/wicd/+bug/993912

Slackware should upgrade to 1.7.3 as soon as that one is out, as version 1.7.2.4 doesn't work at all if you're trying to connect to a new network. Or patch the 1.7.2.4 package anyway.

TommyC7 · 05-04-2012, 08:35 AM

Actually, if I recall you can add a bunch of AP's into /etc/wpa_supplicant.conf and just use rc.inet1.conf to pick whichever one you want to use. If you don't set it, I believe it uses the connection with the best signal.

spudgunner · 05-04-2012, 08:50 AM

Quote:

Originally Posted by TommyC7

Actually, if I recall you can add a bunch of AP's into /etc/wpa_supplicant.conf and just use rc.inet1.conf to pick whichever one you want to use. If you don't set it, I believe it uses the connection with the best signal.

Interesting comment, I'll look into this. Perhaps I'll have to start keeping wpa_supplicant.conf sync'd in Dropbox and copy the new version over every time I install Slackware (assuming I can get an internet connection somewhere).

I'm marking this as solved as it's a known bug (not just me) and it looks like it's gonna get fixed soon.

slackass · 05-04-2012, 02:24 PM

I managed to get wicd working by downgrading to 1.7.0
The problem I was having with kde network manager turned out to be my modem.

spudgunner · 05-04-2012, 03:58 PM

Meh, I can wait for a little while. Ever since I finished school, the laptop gets used for the odd overnight trip for work and for experimenting with Linux. I just went through installing Slackware64 for the first time (having never used a 64-bit distro before) with LVM+LUKS (also the first time for encryption and logical volumes). Other than this bug in wicd that isn't my fault, there weren't any major hiccups. This weekend I'm either playing lots of video games or installing a multilib environment, haven't decided which yet.