[Hardy] knetworkmanager keeps asking for WEP key although it knows it

Bug #196375 reported by gpothier
4
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?

Revision history for this message
Francisco Borges (francisco-borges) wrote :

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.

Revision history for this message
Luka Renko (lure) wrote :

knetworkmanager 0.2.2 is now available in Hardy and have some fixes for handling KWallet passwords that can help with auto-connect.
Can you check if you can reproduce this with up-to-date Hardy?

Changed in knetworkmanager:
assignee: nobody → lure
status: New → Incomplete
Revision history for this message
gpothier (gpothier) wrote :

I haven't seen the problem in a while. Also, automatic reconnections seem to work more frequently.

Revision history for this message
Francisco Borges (francisco-borges) wrote :

I can't reproduce the problem either.

As far as I am concerned, you can close this one, Luka.

Cheers,

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Good evening,

I have still having problems with this bug. I have saved my wireless key in KWallet, when I connect it shows the key stored in the location for the key, but then I need to click on connect to connect.

JOnathan

Revision history for this message
Jonathan Jesse (jjesse) wrote :

No longer having this problem in Intrepid. No problems here. Marking the bug as such

Changed in knetworkmanager:
status: Incomplete → Fix Released
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.