KWallet::openWallet(Synchronous) : time out after 1 hour rather than 25 seconds.
Review Request #127121 - Created Feb. 20, 2016 and submitted
The default DBus timeout is 25 seconds, which means that if the user went to get a cup of tea during session startup, when they come back they get prompted with all sorts of additional non-kwallet password requests due to all kwallet requests having timed out. I added setTimeout in QDBusAbstractInterface in Qt 4.8 for things like this. Testcase: eval `dbus-launch` export SSH_ASKPASS=$KDEDIR/bin/ksshaskpass ssh-add < /dev/null (but the same happens with the IMAP resource etc.)
(see commit log)
Sorry for being the guy who says "I don't like this improvement because it's still not perfect"...
Why have a timeout at all and not, for example, retry after getting a timeout error? (A long timeout still makes sense to avoid most UI glitches)
I hope nobody uses the synchronous API in the UI thread, it would be a terrible idea to do that anyway. Is this for e.g. Akonadi agents? Those could as well wait indefinitely. If they can't -> well they shouldn't use synchronous API. Synchronous IPC to an unreliable peer (if the user is involved it's unreliable ;) is asking for problems.