Version: 0.50.1 (using 4.0.4 (KDE 4.0.4 >= 20080505) "release 11", compiled sources) Compiler: gcc OS: Linux (i686) release 2.6.25.3-2-pae Using KDE 4.0.4 on opensuse 11.0 Beta 3 After giving the password for KWallet, kopete directly tries to connect to e.g. MSN. Not always, but mostly this fails (popup window asking for MSN's password). KWallet is still starting and has not given the passwords yet.
I can confirm this. And if you don't type in the password for kwallet within a very short time kopete asks for the icq password, too. Then I've to fiddle around: click the second dialog away --> type the kwallet password --> right click on kopete icon --> set status --> online. And with a bit of luck kopete goes online then. But its absolutely no smooth experience.
Sorry. Forgot to mention that i'm using Kde 4.1 beta1 on opensuse 10.3
Yes, that's the other part of this bug: after all this, it does NOT go online by itself, not even after a few minutes or longer.
*** Bug 162858 has been marked as a duplicate of this bug. ***
I can confirm this. I log in to KDE (4.0.83) and then do something else. When I come back to my PC I have to supply all password by hand. Kmail has the same timeout problem. Should I open a new bugreport for this?
I think I know what the problem is: 1) kopete sends an open request to the wallet 2) the connection to the wallet times out after 25s 3) you enter the password correctly and the wallet opens 4) but: as the connection kopete<->wallet timed out, kopete doesn't know about it I'm about to prepare a solution for kwallet and hope it will make it into the 4.1 release :)
The timeout problems are fixed now in RC1.
Hi, In 4.1 RC1 this issue was solved ... but in KDE 4.4.1 it seems being back. I've Kopete to start automatically when I log in. The KWallet password dialog box appears. Waiting a while causes Kopete to present it's own logging dialog box. A regression? Do I need to file a new bug? Martin Kho
Why is this marked as RESOLVED FIXED? I don't use Kopete so I can't comment but comment #8 indicates that it wasn't resolved really. I came across this when reporting bug #387056. The solution seems to reside in https://bugs.kde.org/show_bug.cgi?id=154131#c6 talking about DBus timeout. Please check whether this is still applicable to this product.