Yahoo Constantly Disabled

[deadly7]

Pidgin 2.5.1

After staying logged in and not doing anything with YIM for half an hour, Yahoo Instant Messenger arbitrarily disables itself and logs out, saying that signing into the Yahoo! website should fix it. However, simply re-enabling the account works just fine.

[Michael]

Does the a notification pop up saying: "Unknown error number 0. Logging into the Yahoo! website may fix this"? If so, this could be a duplicate of ticket #5223.

[rtaft]

I don't believe this is the same. #5223 has this line: (19:17:00) yahoo: Yahoo Service: 0x7d1 Status: -1 where the current issues does not. This started for me too a few days ago, and judging by the comments on #5223 from the last 3 days, I think this is a recent change on yahoo's part, and issue #5223 is an older issue that is not directly related to this one.

(17:18:10) yahoo: 11 bytes to read, rxlen is 31
(17:18:10) yahoo: Yahoo Service: 0x54 Status: -1
(17:18:10) account: Disconnecting account 02378868
(17:18:10) connection: Disconnecting connection 041F70B8
(17:18:10) connection: Deactivating keepalive.
(17:18:10) connection: Destroying connection 041F70B8

[dandv]

If this is YM timing out, it's inconsistent. On one account, I got booted out after 25 minutes of inactivity. On another one, I'm still logged in fine after an hour and a half. Or maybe "activity" is deep than what I see (e.g. not just IMs but including singn-ons and sign-offs which I ignored).

[Sim-on]

Ticket #7166 has been marked as a duplicate of this ticket.

[Sim-on]

Ticket #7147 has been marked as a duplicate of this ticket.

[Michael]

Interesting. Two errors that are identical on the surface, but are actually different. I hadn't thought of that. I'm not a programmer, so I don't understand the finer points of computer language. Sorry. Glad you corrected me.

[zwoop]

Replying to Sim-on:

Ticket #7166 has been marked as a duplicate of this ticket.

The #7166 ticket has more useful information than this ticket though, since it actually has a suggestion for a solution (reduce the amount of ping requests).

[Sim-on]

Replying to zwoop:

Replying to Sim-on:

Ticket #7166 has been marked as a duplicate of this ticket.

The #7166 ticket has more useful information than this ticket though, since it actually has a suggestion for a solution (reduce the amount of ping requests).

Yeah, this solution sounds well and we've recognized that (and this is part of the discussion in #pidgin now). Thanks to "todo". It is not really important which ticket is now open an will be closed as "fixed" later. but it shouldn't one of the first because other did not search for existing tickets before creating there tickets ;) 7147 i saw later but this has less information than here.

[datallah@…]

(In [092bbcea7b768d21baff3362314e784b26b1ced7]):
Only send a yahoo ping once an hour. The server doesn't like it when send it every 30 seconds. We also send a keepalive every 60 seconds or so like the native client does. I think this fixes #7161

[todo]

Replying to datallah@…:

(In [092bbcea7b768d21baff3362314e784b26b1ced7]):
Only send a yahoo ping once an hour. The server doesn't like it when send it every 30 seconds. We also send a keepalive every 60 seconds or so like the native client does. I think this fixes #7161

When can we role this out? Thanks!

[Sim-on]

Ticket #7183 has been marked as a duplicate of this ticket.

[todo]

Replying to datallah@…:

(In [092bbcea7b768d21baff3362314e784b26b1ced7]):
Only send a yahoo ping once an hour. The server doesn't like it when send it every 30 seconds. We also send a keepalive every 60 seconds or so like the native client does. I think this fixes #7161

Datallah: on a second thought, I think it might be even better if we don't cast the timeout in stone, instead of, we listen to the value that's send down with 143. This way, if Yahoo changes this agian, we won't have to revisit this again.

[datallah]

Replying to todo:

Datallah: on a second thought, I think it might be even better if we don't cast the timeout in stone, instead of, we listen to the value that's send down with 143. This way, if Yahoo changes this agian, we won't have to revisit this again.

I'm not particularly inclined to do that because I'm not confident that is the real purpose of the 143 key.

[Harold_Hawthorne]

I have been having problems with getting disconnected from Yahoo in Pidgin 2.5.1. I've been using Gaim and then Pidgin for years and I've never had this problem before until about 12 days ago. I get disconnected from Yahoo 2 to 3 times a day. I still however remain connected to AIM/MSN through Pidgin and IRC. I am able to login to Yahoo without any problem but i randomly get disconnected. I tried logging into the web Yahoo IM like the error message said and that didn't help. Below is the debugging information.

(00:17:28) msn: C: NS 000: PNG (00:17:28) msn: S: NS 000: QNG 50 (00:17:39) yahoo: 13 bytes to read, rxlen is 33 (00:17:39) yahoo: Yahoo Service: 0x54 Status: -1 (00:17:39) yahoo: 56 bytes to read, rxlen is 76 (00:17:39) yahoo: Yahoo Service: 0x7d1 Status: -1 (00:17:39) yahoo: Unhandled service 0x7d1 (00:17:39) account: Disconnecting account 0x8147100 (00:17:39) connection: Disconnecting connection 0x85253c0 (00:17:39) connection: Deactivating keepalive. (00:17:39) connection: Destroying connection 0x85253c0

[Harold_Hawthorne]

I changed "#define KEEPALIVE_INTERVAL 30" to "#define KEEPALIVE_INTERVAL 120" in pidgin-2.5.1/libpurple/connection.c and recompiled Pidgin. I've left the computer for an hour a few times and came back and I haven't been disconnected. So far so good and I hope it stays that way.. I just couldn't wait for the fix in the upcoming release because I was sick of getting logged out of Yahoo so I tried this as an experiment to see if it fixed it for me.

[datallah]

Ticket #7266 has been marked as a duplicate of this ticket.

[hackel]

I am still experiencing this with Pidgin 2.5.2. I will attempt to get a debug trace the next time it happens.

[hackel]

Still happens with Pidgin 2.5.3. Someone with permission please re-open this bug, unless you believe this to be a new issue, in which case I will open a new bug report.

The debug output doesn't seem to provide much useful information... As it says, logging into the website allows logging in again.

(16:41:53) yahoo: Calculated buddy icon checksum: 241581250(16:41:53) dns: DNS query for 'scs.msg.yahoo.com' queued (16:42:03) dns: Got response for 'scs.msg.yahoo.com' (16:42:03) dnsquery: IP resolved for scs.msg.yahoo.com (16:42:03) proxy: Connecting to scs.msg.yahoo.com:5050 with no proxy (16:42:03) proxy: Connected to scs.msg.yahoo.com:5050. (16:42:03) yahoo: 101 bytes to read, rxlen is 121 (16:42:03) yahoo: Yahoo Service: 0x57 Status: 1 (16:42:03) yahoo: yahoo status: 0 (16:42:03) yahoo: 189 bytes to read, rxlen is 209 (16:42:03) yahoo: Yahoo Service: 0x54 Status: -1 (16:42:03) yahoo: In yahoo_buddy_icon_upload_data_free()

Unknown error number 29. Logging into the Yahoo! website may fix this. http://ab.login.yahoo.com/img/6n1HsuVZFekJHruQk8V2JG9YwjnUcAKZTtVGn_621M0HP8ubrLwNsg--.jpg

The link is to a captcha image.

[hackel]

FYI each time I change IP's I get this error upon connecting, though it also occurs sometimes at random when the connection is dropped. I do not know if this coincides with my home router changing IPs.

[rtaft]

You probably should start a new ticket. This particular disconnect issue is fixed, I no longer get dropped from Yahoo since 2.5.2. Yours sounds like a legitimate security check on yahoo's part. If they are tracking IP's and you change your IP, and that causes you to have to log into the website, then I don't know if there is much pidgin can do for you. Even so, start a new ticket detailing as much as you can, especially details on what causes the error to appear.