[Hardy] knetworkmanager keeps asking for WEP key although it knows it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
knetworkmanager (Ubuntu) |
Fix Released
|
Undecided
|
Luka Renko |
Bug Description
Binary package hint: knetworkmanager
This is a somewhat random bug in Kubuntu Hardy.
Quite often, when the network manager tries to connect to my WEP-encrypted network, the connection attemp times out on DHCP and then knetworkmanager pops up the "Connect to wireless network" dialog where I must enter the WEP key (which seem to indicate that it tried to configure the network interface with a wrong key, hence the DHCP timeout). The funny thing is that in the dialog's passphrase/key field, my hex key is already correctly filled in. The only thing that is incorrect is that the encryption type is set to WEP passphrase instead of WEP hex. I just have to select WEP hex in the combo and validate, and the connection succeeds.
Now the strange thing is that it doesn't happen all the time. Typically it happens when I first start the computer. Then I can suspend/resume many times without problems. It just happens sometimes...
How can I help debug this?
I've been having exactly the same thing with Hardy.
Random requests for a key stored in kwallet. A key which (just like above) is already filled in.