Version: 1.10.3 (using 4.1.3 (KDE 4.1.3), Arch Linux) Compiler: gcc OS: Linux (x86_64) release 2.6.27-ARCH 1. There should not be a timeout at all. Since I configured that I want my passwords kept in the wallet, freakin wait for me to provide access 2. After wrongly asking for the account passwords, KMail drops my configuration. If I do not provide them, KMail can not find them in the wallet next time, and if I do provide them, KMail tries to PREVENT me from keeping them in the wallet by making that the default choice, even I FREAKIN DID CONFIGURE IT TO KEEP THEM IN THE WALLET. 3. This sucks. Bad.
No need to scream, thanks.
On the kwallet side this was due to DBus imposing a timeout on the method call. It used to be 20s however I raised it to around 6 hours in 4.1 (there needed to be some limit however). Starting with 4.2 I worked around this limit so there shouldn't be any timeout at all. However I don't know if kmail imposes an extra limit (don't think it does).
The timout is certainly shorter than 6 hours, more like 5 or ten minutes. Short enough that I feel that I have to sit and wait for the prompt when I log in. OR had to, since my configuration is now messed up and have to be hand edited to work as desired again.
Timeout bug is at bug 170830.
wallet connection times out (FIXED), kmail times out (unsure), kmail account loss (probably FIXED) and kmail looses track of wether the password is stored in configuration or in kwallet (unsure) says lemma, end result, dupping *** This bug has been marked as a duplicate of bug 170828 ***