Bug 161747 - Typing a single character in a Yahoo chat window causes Yahoo to temporarily go offline.
Summary: Typing a single character in a Yahoo chat window causes Yahoo to temporarily ...
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Applications
Component: Yahoo Plugin (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-07 17:26 UTC by Jeff
Modified: 2010-01-17 04:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff 2008-05-07 17:26:14 UTC
Version:            (using KDE 3.5.9)
Installed from:    Gentoo Packages
Compiler:          gcc version 4.1.2 (Gentoo 4.1.2 p1.1) 
OS:                Linux

Typing a single character in a Yahoo chat window causes Yahoo to temporarily go offline.

1) Start Kopete.
2) Enabled my Yahoo account.
3) Click on any one of my Yahoo contacts to initiate chat.
4) The instant I type a single character in my chat window, Yahoo goes offline, then comes back online about 10 seconds later.
5) This happens with all my Yahoo contacts.
Comment 1 Jeff 2008-05-07 23:12:36 UTC
EDIT: I can right-click on Yahoo contacts, and select 'Send Single Message', and this allows me to chat with my Yahoo contacts, but it's just a slight inconvenience seeing that I have to close the window every time in order for it to not disconnect me.

Keep up the great work. KDE is good stuff.

-Jeff
Comment 2 Jeff 2008-06-20 18:03:43 UTC
UPDATE: http://bugs.kde.org/show_bug.cgi?id=163307

This bug is very close to what I've experienced with the 'Error 17: Remote host closed connection'.

Just a quick FYI.
Comment 3 Jeff 2008-06-20 18:21:57 UTC
UPDATE: This has something to do more with my company network me thinks, since I had my wife test her Yahoo connection from home, and it's working fine. She's using the same release of Gentoo/KDE as well.

ARGH!
Comment 4 Marius Cirsta 2008-07-07 02:45:29 UTC
 I'm pretty sure this is caused by the typing notification Kopete is trying to send. User .... is typing a message. But I've got no idea as to why exactly this is , probably something specific about the network as you said.
Comment 5 Steve Hay 2008-07-07 02:46:22 UTC
Recommend using a packet sniffer tools to see what is going on and resubmit.
Comment 6 Jeff 2008-07-07 20:32:06 UTC
What would you recommend for a good packet sniffer?

Thanks again.
Comment 7 Ruud Koolen 2008-07-08 17:39:45 UTC
Try Wireshark (wireshark.org).
Comment 8 Jeff 2008-07-10 16:44:30 UTC
--- Quote ---

------- Additional Comment #4 From Marius Cirsta 2008-07-07 02:45 -------  
 I'm pretty sure this is caused by the typing notification Kopete is trying to send. User .... is typing a message. But I've got no idea as to why exactly this is , probably something specific about the network as you said. 

--- End Quote ---

With this in mind, I disabled my 'Global Identity', which also disables your global buddy icon. Now I can use Yahoo with no problems.

Should I close this ticket?
Comment 9 Jeff 2008-07-10 16:47:33 UTC
Scratch that. Disabling my Global Identity only solved it for a single sentence. I'm back to it dropping me again. *sigh*

I have some of my network peoples looking into it as well. Would love to be able to stomp this bug (or my network - whichever comes first).
Comment 10 Jeff 2008-07-14 21:42:30 UTC
UPDATE: Had my network peoples help me out a bit. Here's a snip from him:

"should only be using port 5050 to scs.msg.yahoo.com"

So, in 'Settings' --> 'Accounts', I go to my Yahoo account's settings, and try to override the default server, entering the info above. I can enter it fine, but Kopete doesn't seem to want to *save* it. 'Apply' doesn't highlight or come to life, and I'm ending up just clicking 'Ok', and then when I go back to the account settings, I notice that the server override was *not* saved.

Just a quick FYI.
Comment 11 Matt Rogers 2010-01-17 04:13:37 UTC
I couldn't reproduce this with the upcoming KDE 4.4 release.