Version: 0.11.93 (using KDE KDE 3.5.2) Installed from: Compiled From Sources Compiler: GCC 4.1.0 OS: Linux On dialup (with Gentoo in KDE, et cetera), when automatic reconnects to dialup are completed, Kopete mostly reconnects properly, but with the AIM protocol, the reconnect never completes at least as long as there's any other network activity going on, such as a download. If you stop all other meaningful network traffic, then disconnect and manually reconnect it then, it works, but not as long as there's apparently any other activity.
i would need debug output from the console to see where it stalls during reconnect.
no debug output and i have no dial up to reproduce this with. Please reopen if you can provide more information.
I'm seeing something like this, but without a dialup connection. It almost never happens when it's the first time Kopete connects to AIM, but it almost always happens on reconnects. I haven't had a chance to fully diagnose it, but the only significant difference on the wire is that, once authorization finishes successfully, Kopete opens a connection to the new server and sends the "BOS SignOn" command before the "Connection Acknowledge" message gets received, at which point the server disconnects silently. The little blue guy then walks forever. When Kopete sends the "BOS SignOn" after receiving the "Connection Acknowledge" everything proceeds normally.
Created attachment 16040 [details] tcpdump of failing connection
Created attachment 16041 [details] kopete debug output
reopening. VERIFIED means that the resolution of the bug has been verified by someone other than the person fixing the bug.
SVN commit 540531 by rjarosz: Fix bug when ICQ or AIM status icon stays turning forever if connection is closed on login. CCBUG: 124987 M +5 -2 client.cpp --- branches/kopete/0.12/kopete/protocols/oscar/liboscar/client.cpp #540530:540531 @@ -1211,8 +1211,11 @@ if ( !c ) return; - if ( c->isSupported( 0x0002 ) ) - emit socketError( code, string ); + if ( c->isSupported( 0x0002 ) || + c->supportedFamilies().count() == 0 ) //emit on login + { + emit socketError( code, string ); + } //connection is deleted. deleteLater() is used d->connections.remove( c );
*** Bug 139529 has been marked as a duplicate of this bug. ***
This bug is probably fixed in trunk ( commit r661505 ), because only diffrence from official client is that we don't send Close Connection FLAP.
Does this problem still exist with a recent KDE 4 version of kopete?
No response, if you still see this bug in KDE 4.1 or greater please reopen.