Wicd problem with wep after upgrading to 9.04

Bug #369162 reported by trevonio
2
Affects Status Importance Assigned to Milestone
wicd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: wicd

Since wicd is not part of ubuntu I don't know If this is the right place to report it. Please tell me.

Using Wicd 1.5.9 as network manager. When I boot the computer wicd can connect with my router (configured with wep) without problems and I have internet connection. After a while the connection goes down. When that happens I click in wicd and I can see only the wifi signal from my router but no others (usually I receive signals from 6 or 7 routers).

After that the only way to connect again is reboot ubuntu. I see again all the signals and click in mine.

Some relevant data:
I've just updated to ubuntu 9.04. Before that I had no problems at all.
I can connect with other routers so I think must be a problem of wicd and wep.

Revision history for this message
Andrew Reid (reidac) wrote :

I am also seeing similar behavior. I just installed Kubuntu 9.04 on an old Sony PCG-R505ECK laptop. I can set up wireless connections manually using ifconfig and iwconfig, but wicd can't do them. It has correct settings, but seems to be trying to run wpasupplicant, even though my connection is WEP, and the desktop widget correctly set for WEP/HEX. I notice that, when trying to get wicd to connect from a fresh boot, iwconfig does not report that the key has been assigned, only that the ESSID has been.

The part of this that is relevant to the report above is that, after it fails to connect, I've noticed that, coincident with momentary graying-out of the desktop widget, the channel gets changed on the wireless device (detected via "iwlist <device> frequency") I can't seem to change it back, even after I stop the wicd daemon.

I suspect (guessing, really) that the basic bug is the attempt to use a wpa scheme for wep encryption, and that the channel-changing is a side-effect of failing to connect in the first place.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.