I run in to a problem if -- right after I log in -- a wireless password (stored in kwallet) is needed before kwallet is unlocked. Reproducible: Always Steps to Reproduce: 1. On startup, the computer tries to connect to a password protected wireless network before I have time to unlock the wallet. 2. If I enter the kwallet password in the dialog box, then the wireless remains stuck in "waiting for authorization" mode. 3. If I then enable and disable the wireless, the kwallet password dialog box pops up again, with the password already entered in it, but hitting enter still won't get the wireless to connect. The only solution I've found is to kill kwalletd. Then when I can start connecting to the wireless network, enter my password, and things work fine. PS. If I'm really fast and manage to unlock kwallet before the computer tries to connect to a password protected wireless network, then this isn't a problem. In other words, this wouldn't be a problem if single sign-on were implemented...
Created attachment 78359 [details] This is what I see in step 1. The wireless is trying to connect to a secure network (note key over wireless widget in system try) -- before I've managed to unlock kwallet.
Created attachment 78360 [details] This is what I see in step 2. I've entered the password, but it's still "waiting for authorization".
Created attachment 78361 [details] This is what I see in step 3. I've disabled and enabled the wireless, and it's again asking for my password. However, this time, the password is already entered in the dialog box.
I can confirm this exact behaviour.
confirm bug. It always happens if i'm not there to enter my k-wallet password fast. Then I have to uncheck "Enable KWallet subsystem" from KDE Wallet Configuration, hit Apply, wait few seconds, Enable again. Open my wallet from KWalletManager, enter password. If I don't do this, it will not work and ask for password all the time, passwords that won't work.
I can confirm this occurs to me too with the exact same steps and symptons. I am running Kubuntu 13.04. The only way to fix the issue is by killing the kwalletd service and trying to reconnect to wireless again.
Was looking at the kwallet bugs, could this bug be related to https://bugs.kde.org/show_bug.cgi?id=319138?
It may well be. On that page, someone mentions Bug 254198, which might be the root cause of both.
*** This bug has been confirmed by popular vote. ***
*** This bug has been marked as a duplicate of bug 254198 ***