Version: 1.1 (using KDE KDE 3.5.1) Installed from: Ubuntu Packages OS: Linux I think this bug may be covered in other posts, but they were not clear. When my kde-session starts up both kontact and kopete attempt to access the same kwallet. This seems to cause a race condition, and both processes are in a wait lock. Killing one of the processes or removing it from the session autostart allows kwallet-manager to open the wallet, and the password dialog (which doesn't take the keyboard focus, arrgghh) comes up. How to reproduce: Load two applications (in this case kontact and kopete) which have passwords stored in kwallet at session start. Expected Behavior: The two applications hang, while waiting for access to the kwallet. -- Tim
I am seeing this on kde 3.5.2-meta on Gentoo, any time that two apps try to access the wallet simultaneously they hang the whole of kde - probably just need to find the right konqueror process to kill. I use Alt-F2 a lot and opening websites that have passwords from there repeatedly, while kontact is launching causes this to happen reasonably often. I get this maybe once or twice a week.
This is probably no longer the same bug but I do currently see a similar race condition in trunk (probably KDE 4.1 too). It only happens sometimes and I haven't looked into it yet.
Haven't seen a race condition for quite a while now. I hope I fixed it :)
I still experience a race condition. When starting up both akonadi and chromium wants to use the wallet. A password dialog shows up requesting me to open the wallet but it doesn't actually open. I usually stop akonadi, killall kwalletd and then open the kwallet manually by starting kwalletmanager. Then I can start akonadi again and everything works.
Update: I'm sorry, I didn't check the bug report list properly. Apparently the behaviour I described in my previous post is handled by bug #254198 and it seems to have been fixed in KDE 4.11.2 (I'm still on 4.10.5)