Pidgin

Ticket #5223 (closed defect: out of date)

Opened 2 years ago

Last modified 21 months ago

Pidgin disconnects from Yahoo! Chat with Unknown error number 0. (regression)

Reported by: Karmadon Owned by: marv
Milestone: Component: Yahoo!/Yahoo! JAPAN
Version: 2.5.1 Keywords: error number 0
Cc: co152, Michael, jsharper, gribelu, Gizmokid2005, zidynnala, sk8geek, alastairb, Root

Description

Very often Pidgin 2.4.0 disconnects from Yahoo and dialog box pops up:"Unknown error number 0. Logging into the Yahoo! website may fix this". In the same time Pidgin 2.3.1 works excellent.

Debug window output during this error:

(19:17:00) yahoo: 22 bytes to read, rxlen is 42
(19:17:00) yahoo: Yahoo Service: 0x54 Status: -1
(19:17:00) yahoo: Key: 1 Value: karmadon3
(19:17:00) dbus: Need to register an object with the dbus subsystem. (If you are not a developer, please ignore this message.)
(19:17:00) dbus: The signal "account-error-changed" caused some dbus error. (If you are not a developer, please ignore this message.)
(19:17:00) yahoo: 10 bytes to read, rxlen is 30
(19:17:00) yahoo: Yahoo Service: 0x7d1 Status: -1
(19:17:00) yahoo: Key: 66 Value: 1014
(19:17:00) yahoo: Unhandled service 0x7d1
(19:17:00) account: Disconnecting account 0x81b6470
(19:17:00) connection: Disconnecting connection 0x8973478
(19:17:00) connection: Deactivating keepalive.
(19:17:00) connection: Destroying connection 0x8973478
(19:17:06) util: Writing file accounts.xml to directory /home/karmadon/.purple
(19:17:06) util: Writing file /home/karmadon/.purple/accounts.xml

Change History

follow-up: ↓ 2   Changed 2 years ago by datallah

Is this related to yahoo chats, or are you just referring to the overall IM protocol?

I don't think this is likely to be related to 2.4.0 - it is more likely a server blip or something.

in reply to: ↑ 1   Changed 2 years ago by Karmadon

Replying to datallah:

Is this related to yahoo chats, or are you just referring to the overall IM protocol?

I do not know for sure. But in chats it happens oftener.

I don't think this is likely to be related to 2.4.0 - it is more likely a server blip or something.

I tried several times to install 2.4.0 on different computers and then rolled back to 2.3.1. The latter works like a charm. However it may be a Gentoo ebuild issue. I'll try to install vanilla sources.

  Changed 2 years ago by sulabh.dev

Ticket 5500 is related Yahoo Service: 0x54 Status: -1 means that authentication was rejected. Reason would be evident from the values of the key-pairs. This in no way is a pidgin bug. It probably is that CPATCHA thing

The unknown part ie Yahoo Service: 0x7d1 Status: -1. yahoo: Unhandled service 0x7d1 is yahoo server telling the client to disconnect. 0x7d1 is a way the server tells the client to disconnect, like when we supply bad username/password, or when authentication is rejected, or when someone signs on from another location. Right now we don't care about 0x7d1, we just disconnect.

  Changed 2 years ago by bernmeister

Does this still occur in 2.5.1? Can you please verify?

follow-up: ↓ 6   Changed 2 years ago by Sim-on

  • status changed from new to pending

in reply to: ↑ 5   Changed 2 years ago by co152

Replying to Sim-on: I started having this problem about a week ago with version 2.3. It happens about 2-3 times a day at random times and didn't seem to matter whether I was chatting at the time or not. As I often stay logged in, in Away mode overnight or during the day, I'd return and find the error. Using Pidgin about 8 months now and never had this problem before. I upgraded to 2.5.1 and that doesn't seem to make a difference. I can login to Yahoo or use Yahoo Messenger ok. HTH!

  Changed 2 years ago by Myste

Been having this problem the last 2-3 days with pidgin 2.4.1 on Ubuntu. Upgraded to 2.5.1 last night and the error occurred once again overnight.

  Changed 2 years ago by Michael

I can confirm it happens on my 2.5.1 version, too. It happens in the same manner and frequency as co152 noticed. Mine is on Windows XP SP3, though.

  Changed 2 years ago by martinsauter

It started to happen to me, too in the last couple of days. I upgraded to Pidgin 2.5.1, rebooted but the problem persists. Still getting "Unknown error number 0. Logging into the Yahoo! website may fix this." in connection with my yahoo account every couple of hours. Once I click on "re-enable", everything is fine again until it occurs again.

  Changed 2 years ago by jsharper

I, too, started having this problem in the last 2-3 days with 2.4.3. I upgraded to 2.5.1 and the problem persists.

  Changed 2 years ago by Squirrelly

I'm just started getting this issue as described above too, even with Pidgin 2.0.0 which I've had installed on a work computer for some time, but only rarely ever saw before, if at all. It may be something yahoo is doing different now.

  Changed 2 years ago by Sim-on

  • status changed from pending to new
  • version changed from 2.4.0 to 2.5.1
  • summary changed from Pidgin 2.4.0 disconnects from Yahoo! Chat with Unknown error number 0. Pidgin 2.3.1 works fine. to Pidgin disconnects from Yahoo! Chat with Unknown error number 0. (regression)

  Changed 2 years ago by gribelu

I have the same problem with 2.5.1

If you need further debugging i'd be glad to help just let me know how.

  Changed 2 years ago by martinsauter

I have observed and traced the problem twice today with Wireshark. The problem appears when the Yahoo server sends an "Authentication Response (Status disconnected)" messages to the client. Prior to this message, only status messages and TCP acknowledgments every 30 seconds can be observed. Hence, the authentication response message was not provoked by Pidgin. The full Wireshark trace is available on request (gsmumts at gmx.de). Here's an ASCI dump of the message sent by the Yahoo server (username changed):

Source: 66.163.181.188 (66.163.181.188) Destination: 192.168.40.71 (192.168.40.71)

Transmission Control Protocol, Src Port: mmcc (5050), Dst Port: dlms-cosem (4059), Seq: 313, Ack: 4315, Len: 46

Source port: mmcc (5050) Destination port: dlms-cosem (4059) Sequence number: 313 (relative sequence number) [Next sequence number: 359 (relative sequence number)] Acknowledgement number: 4315 (relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK)

0... .... = Congestion Window Reduced (CWR): Not set .0.. .... = ECN-Echo: Not set ..0. .... = Urgent: Not set ...1 .... = Acknowledgment: Set .... 1... = Push: Set .... .0.. = Reset: Not set .... ..0. = Syn: Not set .... ...0 = Fin: Not set

Window size: 65535 Checksum: 0x2174 [validation disabled]

[Good Checksum: False] [Bad Checksum: False]

[PDU Size: 46]

Yahoo YMSG Messenger Protocol (Authentication Response)

Version: 15 Packet Length: 26 Service: Authentication Response (84) Status: Disconnected (4294967295) Session ID: 0x043e4800 Content: 1\300\200xxxxxxxxxxxxxxxxxxxxx\300\200

1:xxxxxxxxxxxxxxxxxxxxx

Key: 1 Value: xxxxxxxxxxxxxxxxxxxxx

  Changed 2 years ago by captaincrook

Confirming the bug has appeared for me, although within the past 2 days. Upgraded from 2.5.0 to 2.5.1 with no change. Using Xubuntu Hardy.

  Changed 2 years ago by MrGibbage

Add me to the list. Using 2.4.2 on Vista x64 and just started getting this error message about three or four days ago.

  Changed 2 years ago by SuMarDi

I have the same problem. Tested with finch 2.4.0-1.fc8 and 2.3.1-2.el5_2.

  Changed 2 years ago by Gizmokid2005

I can confirm this is an issue that started with 2.5.1 on XP Pro SP2 just starting ~3 days ago.

  Changed 2 years ago by zidynnala

Add me to the list of people with this error. 2.5.1 on XP Home SP2 at home, starting a few days ago. Version 2.3.1 (a self built portable version) on XP Pro at work starting around the same time. Seems to do it randomly, but at least every 5 hours. It doesn't matter if I'm active or if the computer has been idle - I've been both away and available and it did it. I only have the one account so I don't know if I had two online through Pidgin if it'd give me the error at the same time.

  Changed 2 years ago by sk8geek

I only started seeing this problem a few days ago. Running 2.5.0 on Fedora Core 6.

  Changed 2 years ago by xyon

I don't think this is a bug with pidgin, it's something new that Yahoo is doing, IMO. Seems they've unified their email/messenger logins? I wonder if there is a way around this?

  Changed 2 years ago by snstanton

I'm using 2.5.1 on XP Pro SP2 and started seeing this problem over the weekend. It seems likely to be a Yahoo issue of some sort since it started without any software changes.

  Changed 2 years ago by rtaft

Given that this ticket is 6 months old, and the issue everyone is experiencing started 3 days ago, I don't think this is the exact same issue. There is also ticket #7161.

  Changed 2 years ago by Sim-on

  • status changed from new to closed
  • resolution set to out of date

i just did a research about ticket to this issue and found a lot of duplicates ;) We have too many tickets for this issue. Thanks, rtaft, for pointing out the difference here.

  Changed 2 years ago by gribelu

What other tickets? I searched trac and they are all closed.

Also the debug window output is exactly the same when it disconnects so it is the same problem.

Glad you like closing tickets though, thank you.

  Changed 2 years ago by rtaft

They are closed because the issue is believed to be fixed in code. We just have to wait for 2.5.2 to be released. They are probably testing the fix to make sure this does fix it. If you are in a hurry, there is always the option to compile from source.

  Changed 21 months ago by markdoliner@…

(In [97d295a04f3a9852a3b29cf0df43d56d1ddcc672]):
Two functional changes here: 1. The default error case for unknown errors on yahoo now uses

PURPLE_CONNECTION_ERROR_OTHER_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because it's logical.

2. The unknown yahoo error with error code "0" now uses

PURPLE_CONNECTION_ERROR_NETWORK_ERROR instead of PURPLE_CONNECTION_ERROR_AUTHENTICATION_FAILED. This change was made because this error doesn't seem to be fatal, and we want the account to be reconnected, but normally AUTHENTICATION_FAILED errors are fatal and should not be reconnected

Specially this makes yahoo accounts auto-reconnect when we get the error "Unknown error number 0. Logging into the Yahoo! website may fix this." I know we think we fixed this with that change to send the timeout or keepalive much less often, but I'm still seeing a lot of disconnects for it and I have a strong suspicion that they're not actually fatal errors.

Refs #5223

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!