Bug 124987 - AIM connection sometimes hangs
Summary: AIM connection sometimes hangs
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: ICQ and AIM Plugins (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 139529 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-04-05 18:58 UTC by Kirjah Salys
Modified: 2008-12-28 11:53 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
tcpdump of failing connection (2.88 KB, application/octet-stream)
2006-05-12 16:56 UTC, Matthias Granberry
Details
kopete debug output (65.67 KB, text/plain)
2006-05-12 16:58 UTC, Matthias Granberry
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kirjah Salys 2006-04-05 18:58:33 UTC
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.
Comment 1 Matt Rogers 2006-04-09 01:29:44 UTC
i would need debug output from the console to see where it stalls during reconnect.
Comment 2 Matt Rogers 2006-05-06 17:23:29 UTC
no debug output and i have no dial up to reproduce this with. Please reopen if you can provide more information.
Comment 3 Matthias Granberry 2006-05-06 18:29:40 UTC
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.
Comment 4 Matthias Granberry 2006-05-12 16:56:42 UTC
Created attachment 16040 [details]
tcpdump of failing connection
Comment 5 Matthias Granberry 2006-05-12 16:58:00 UTC
Created attachment 16041 [details]
kopete debug output
Comment 6 Matt Rogers 2006-05-12 20:18:38 UTC
reopening. 

VERIFIED means that the resolution of the bug has been verified by someone other than the person fixing the bug.
Comment 7 Roman Jarosz 2006-05-13 21:53:58 UTC
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 );
Comment 8 Roman Jarosz 2007-05-06 10:50:16 UTC
*** Bug 139529 has been marked as a duplicate of this bug. ***
Comment 9 Roman Jarosz 2007-05-06 10:57:44 UTC
This bug is probably fixed in trunk ( commit r661505 ), because only diffrence from official client is that we don't send Close Connection FLAP.
Comment 10 Roman K. 2008-07-07 15:23:26 UTC
Does this problem still exist with a recent KDE 4 version of kopete?
Comment 11 Roman Jarosz 2008-12-28 11:53:23 UTC
No response, if you still see this bug in KDE 4.1 or greater please reopen.