SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Thanks for the heads-up. I can give that a try. Would a symlink from /usr/lib/python2.5/site-packages/ to /usr/lib/python2.6/site-packages/ work? I may give that a try.
Regards,
The problem is that wicd-1.6.6.2 installs stuff in the python2.6 directory that doesn't get removed when you removepkg. The older version wicd-1.5.9 installs stuff in the python2.5 directory. (And I'm talking about wicd-1.5.9, not the 1.5.6 that came with Slackware 12.2, the 1.5.6 never worked quite right for me.) You want to be sure that you're using the older wicd stuff. Any way you can accomplish that will be fine.
Wicd can also be installed from the source tarball. Just look at the INSTALL file. Beware, it isn't the usual configure / make / make install. The problem I had is that after you run the python setup you have to manually retrieve scripts from the tarball and put them in the right places in Slackware (specifically /etc/rc.d/rc.wicd and the startup scripts for wicd and wicd-client). But for someone who knows a little more than I do, installing directly from the wicd project's source tarball might be easier.
I'm using 'wep-hex' without difficulty. The logs below do show that the devices were set and recognized differently. 'eth0' has not been the recognized device for wireless but for some odd reason wicd started to set the device to the wired interface. Checking the ''/etc/udev/rules.d/70-persistent-net.rules' did not seem to change.
I disabled the wireless in the BIOS then did my replacement for 'wicd 1.6.2.1' to 'wicd-1.6.2.2'. As I stated earlier the remove package for 'wicd-1.6.2.1' show some warnings with stale files left. I removed all these files. I then built my wicd.SlackBuild and installpkg. After that I copied the saved wireless-configuration to '/etc/wicd'. Re-enabled the wireless in BIOS and on the re-boot then boot to get my wireless. The difference being device assignment. ??
Shadowsnipes, the point seems to be that the newest version doesn't connect to WEP-protected networks for some of us. I downloaded and ran the version in -current to no effect.
I understand the problem. I just mentioned the SlackBuild because it sounds like some people are using SW13 or -current packages for 12.2 (or vice versa) and wondering why files are in the wrong python folders. If you use the SlackBuild, the correct version of python will be detected and the files will go to the appropriate place.
I understand the problem. I just mentioned the SlackBuild because it sounds like some people are using SW13 or -current packages for 12.2 (or vice versa) and wondering why files are in the wrong python folders. If you use the SlackBuild, the correct version of python will be detected and the files will go to the appropriate place.
Thanks for the tip.
ETA: That works nicely. I got wicd-1.5.9.tar.gz straight from the wicd project's repository. It's in gzip format instead of the bzip2 that the slackbuild script expects. Anyway, I untar'd the slackbuild, copied in wicd-1.5.9.tar.gz, then edited wicd.Slackbuild as follows:
In other words I edited the version number, the build code, changed it to expect a gz source archive instead of a bz2, and removed the --backends and --wicdgroup options which are not supported by the wicd-1.5.9 package.
Works real fine for me. I wish I could help debug the actual problem to a lower level, but this workaround gets me by. Thanks.
Last edited by DavidHindman; 10-17-2009 at 11:59 AM.
Reason: Add details
I understand the problem. I just mentioned the SlackBuild because it sounds like some people are using SW13 or -current packages for 12.2 (or vice versa) and wondering why files are in the wrong python folders. If you use the SlackBuild, the correct version of python will be detected and the files will go to the appropriate place.
Ah ha, now I see where you're going. Okay, I'll try downgrading to the older version of Wicd, but I'll use the Slackbuild script from Slackware 13, suitably modified, to build the package.
Interestingly, I had an ESSID problem with wicd 1.6.2.2 on Slackware 13.0. For some reason the program kept trying to connect to a network with no name (even though I was using a profile for a named network), and I could not change it manually with iwconfig! I was essentially locked until I killed wicd, and then the ESSID would change properly. If I turned wicd back on before having an IP if would lose the ESSID, but if I already had an IP then it would accept the network settings!
At the time I was trying to connect to a WEP network with a hex code. The profile I had created had the correct code and also the correct passphrase. To fix all of these issues I simply killed wicd, removed the wireless-settings.conf, restarted wicd, and manually configured my profile again. This time, however, I used wep-shared instead of wep-hex. I did not give it the passphrase, but only gave it the hex code. Now everything works fine!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
