Version: 4.2.1 (KDE 4.2.1) "release 108" (using 4.2.1 (KDE 4.2.1) "release 108", KDE:KDE4:Factory:Desktop / openSUSE_11.1) Compiler: gcc OS: Linux (x86_64) release 2.6.27.19-3.2-default The subject says it all. When I go to mail.yahoo.com and attempt to login, konqueror offers to store my username and password in kwalletmanager, but nothing ends up stored, and on next attempt to login into mail.yahoo.com my previously entered username and password are not automatically filled in. Inspecting the contents of the kwallet via kwalletmanager reveals no mail.yahoo.com related form data.
Does this only happen for mail.yahoo.com or for other websites as well? After asking you to store the password, did the dialog for opening the wallet pop up or was the wallet already open?
Happens with other websites as well. The wallet was already open. I've just tried closing the wallet and then starting konqueror and opening mail.yahoo.com. Konqueror offers to store the password, but the dialog for opening the wallet never pops up.
Other kde4 apps such as kontact, kopete and gmail-notifier plasmoid are still able to use kwallet for username/password storage without any issues.
That basically means that kwallet is functional but konqueror has trouble using it. I'll have to leave this to some konqueror developer to figure out I fear.
I managed to save and restore data from kwallet to login at yahoo.com and gmail.com. I tested for both sites the scenarios with kwallet closed and already opened and the wallet dialog appeared correctly when needed. My settings: Konqueror Version 4.2.92 (KDE 4.2.92 (KDE 4.3 >= 20090617)) Using KDE 4.2.92 (KDE 4.2.92 (KDE 4.3 >= 20090617)) - svn r984201 qt-copy r978427
Works here too in KDE SC 4.3.90.
Still does not work in KDE 4.3.4 for x86_64 from openSUSE build service. (Konqueror reports version 4.3.4 (KDE 4.3.4) "release 2"). Other applications (like amarok, kopete or BBC iPlayer!!!) work just fine with kwallet. Konqueror is the only one that's broken.
Works fine for me with KDE 4.6.5. If you still have this issue with KDE >= 4.6.5, please test with a new user account and if it still happens, reopen.