Bug 136981 - Never connects to AIM
Summary: Never connects to AIM
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-07 03:33 UTC by David
Modified: 2006-11-10 12:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David 2006-11-07 03:33:08 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Before updating KDE to 3.5.5, Kopete connected to YahooIM and AIM just fine. Now it connects fine to YahooIM, but the AIM icon never stops walking. I cannot initiate any AIM chats - it tells me that I'm not connected. Yet if one of my AIM buddies starts a chat with me, the chat window opens up and I can chat with no problems.

I have no problems connecting to AIM with gaim.
Comment 1 Brandon Huber 2006-11-07 06:11:43 UTC
I can't confirm others being able to message me first on GAIM, but have the infinite running-man problem on my end, also.  I have Kopete 0.12.3, under Debian Etch.  Worked fine under Debian Sarge.  
Interestingly, if I connect or disconnect to my AIM login using GAIM, it seems to stop the little running AIM guy in Kopete, though still none of my AIM contacts show in Kopete.  Note: Both GAIM and Kopete are set to use the same AIM account.
Comment 2 David 2006-11-07 09:35:55 UTC
For me, connecting or disconnecting via GAIM makes no difference at all to the AIM guy in Kopete. When Kopete was working with AIM in the past, if I also used GAIM to connect to AIM, the connection to Kopete would disconnect. Also vice versa (connecting first with GAIM, then connecting simulatneously with Kopete, would disconnect GIM).
Comment 3 Fabian 2006-11-07 16:26:30 UTC
I have the same problem with the AIM guy walking and never connecting, my contacts at AIM can start the chat too but I can't. I have no problems with my MSN, Yahoo accounts. 
I have a RedHat AS 4.0 with KDE 3.5 at work and Suse 10.0 at home, the same problem in both systems.
Everything was working fine until a couple days ago, I haven't changed anything in my systems. AOL people might have touched their protocol.
Comment 4 David 2006-11-07 19:58:33 UTC
If AOL tweaked their protocol, then why is GAIM still able to connect? I didn't start having this problem until I updated Kopete to 0.12.3.
Comment 5 Jan Ritzerfeld 2006-11-07 23:23:52 UTC
Indeed, AOL changed something. Thereby, ICQ was affected by similar problems, that is, neverending connecting. See Bug 136566, that has been fixed. Since I do not use AIM, I do not know whether this AIM problem were fixed, too.
Comment 6 David 2006-11-08 00:45:55 UTC
Well, I'm still not able to connect to AIM. I read bug #136566 and tried some of the things people mentioned, but it makes no difference. While that bug may say it is fixed, I guess the fix didn't get into Kopete 0.12.3. Guess I'll just have to wait until the fix finally shows up ... I'm also just an ordinary user, with no interest in patching and compiling source code.
Comment 7 Jan Ritzerfeld 2006-11-08 09:18:57 UTC
Which version of the debian package do you use? The ICQ problem was found in kdenetwork/4:3.5.5-1 and fixed in kdenetwork/4:3.5.5-2. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=396391
Comment 8 Joe Morris 2006-11-08 13:36:14 UTC
I can confirm the same problem exists with openSUSE 10.1 and 10.2, Kopete version 0.12.3, kde 3.5.5, but IIRC it started after updating, so I believe AOL changed something which broke Kopete's AIM protocol.
Comment 9 Joe Morris 2006-11-08 13:50:30 UTC
I just tried configuring a global identity (actually already enabled, just added a picture file), and it went online immediately.  I got the idea from http://bugs.kde.org/show_bug.cgi?id=136566#c29
Comment 10 David 2006-11-09 00:07:12 UTC
Well, I tried configuring and enabling a global identity as indicated by that post in bug #136566. The only result was that the running man stopped. It doesn't show any of my AIM buddies, and attempting to add an AIM buddy tells me that I'm offline.
I'm sorry that the developers feel it necessary to blame AOL for tweaking something about their protocol, but I seriously doubt that AOL goes around tweaking its protocol to quit working ONLY with Kopete. My daughter has no problem connecting with her non-AOL Windows chat client. My Mac-using friends have no problems connecting with their OS X chat client. Like I mentioned earlier, I'm able to connect with no problems using GAIM. So whatever (if any) "tweaks" AOL may have done don't seem to bother GAIM's implementation of the AOL protocol. Perhaps the Kopete developers could consider replacing their seemingly-more-fragile implementation of the AIM protocol with the one used by GAIM?
Comment 11 David 2006-11-09 00:14:09 UTC
Re comment #7 - I have 3.5.5.1 installed here. I just did a reload in Synaptic, and I see that Debian is up to 3.5.5.dfsg.1-1. I'll try the update, but it doesn't show any updates for Kopete. It does for GAIM.
Comment 12 David 2006-11-09 00:26:11 UTC
Updated from 3.5.5.1 to 3.5.5.dfsg.1-1. No change in Kopete. The running man stops running and looks like it's connected - but there is no connection. No AIM buddies. Can add an AIM buddy, but trying to connect with them gives me the message that I'm not online. Guess I have to wait until 3.5.5.2 shows up.
Comment 13 David 2006-11-10 11:59:36 UTC
3.5.5.2 just hit my repository and has fixed the AIM connection problem. Thank you very much!
Comment 14 David 2006-11-10 12:00:27 UTC
Fixed by Kopete 3.5.5.2 update.