Comment 20 for bug 86680

I'm also having this problem. When knetworkmanager first tries to connect to my wireless network, it asks me for the WEP password for my network. After I enter it, it just sits there with the gear spinning (apparently at 0%). When I check the wallet, there is no entry for knetworkmanager, so it did not successfully create the keystore. If I run knetworkmanager --nofork, I get this on the console:

** (process:20494): CRITICAL **: nmu_security_serialize_wep_with_cipher: assertion `(key_format == IW_AUTH_KEYFORMAT_HEX) || (key_format == IW_AUTH_KEYFORMAT_ASC || key_format == IW_AUTH_KEYFORMAT_PASS)' failed

** (process:20494): CRITICAL **: nmu_security_serialize_wep_with_cipher: assertion `(key_format == IW_AUTH_KEYFORMAT_HEX) || (key_format == IW_AUTH_KEYFORMAT_ASC || key_format == IW_AUTH_KEYFORMAT_PASS)' failed
Serialization of encryption payload failed (key reply).

I haven't started digging into the source to figure out why this would be, but all of this suggests to me that knetworkmanager is probably failing to connect to the wallet. It is not, however, giving me any direct indication that this is what happened, much less how to fix it. I can use iwconfig to set the essid and key manually, then run dhclient ath0, and a connectivity is restored. However, since knetworkmanager still thinks the connection is down, KDE apps like Konqueror and Kopete misbehave.

Please feel free to contact me if you need additional information.