Version: 3.4.3 (using KDE KDE 3.4.3) Installed from: Ubuntu Packages OS: Linux Everything was working, then I tried to connect to a hotel network - it wouldn't work through wireless (via a wireless hub) although it worked in WinXP. Now none of my wireless connections work in Kubuntu. The configurations look OK, in fact, I've changed it slightly and then changed it back, but I can't get a connection. If I "Scan for Networks" I can see the ones I'm supposed to (two of the ones I try to connect to don't broadcast SSID). I just can't get a connection when I select and try to activate the configuration. If I run ifup wlan0, I get the error referenced above, "Error for wireless request "Set Encode" (8B2A) : invalid argument ...". I can't find any documentation stating where the config information is kept, so I haven't been able to check to see if it got corrupted somehow. I tried un-installing KWiFiManager and re-installing, no luck, although uninstalling didn't erase my existing configurations, so if that's the problem, uninstalling wouldn't help, would it. Thanks for any help, sorry if this really isn't a bug, but I thought this would be the best way to contact you. Not really related, but looking at some of the additional features you've added to the new version (more than 4 configurations, the ability to select the network from the scan window look really great, hopefully kubuntu will include them soon.)
*** Bug 129908 has been marked as a duplicate of this bug. ***
The configuration file is called kcmwifirc and is usually located in root's kde dir, something like: /root/.kde/share/config/kcmwifirc. Try renaming it and use the GUI to enter the informaiton newly. The error message about invalid argument _may_ be because there's a bogus encryption key in the config. But you did check that, didn't you? In any case: if it works, it may be interesting to look into the config files (the old, renamed one and the new one) to see what caused the error.
Did you do as proposed in comment #2? I'll close the bug in one week from now if I don't hear from you since it is impossible to move on with resolving this bug without further info.
You can close the bug. I think at this point it more of a feature request. It would be nice to be able to setup and modify the protection using amember control panel even if it is done using an apache .conf file in /etc/apache2. Thanks for the help.
I just got up, didn't have a coffee yet and have no fscking idea what you're talking about. apache2? WTF? But if you say I can close the bug, I'll do so. Maybe what you wrote makes more sense when I'm awake.
Sorry, not your fault, I didn't look at the bug closely and thought it was for something else I recently requested help for. You can close the bug, I resolve the problem by running "sudo ifup wlan0" after configuring the wireless with KiWiFiManager. Not sure why I need to do it when I didn't before, but it's not a problem. Sorry about the other reply, I wasn't paying enough attention.
Never mind, you caught me in my pre-coffee mood. Have fun.