Opened 12 years ago

Closed 8 years ago

Last modified 8 years ago

#1449 closed defect (fixed)

Can't join AIM chatrooms (only sometimes; Pidgin doesn't crash)

Reported by: Refinery Owned by: MarkDoliner
Milestone: 2.7.11 Component: AIM
Version: 2.0.1 Keywords: AIM chat room join
Cc: Rui, yvh11a, Jade, Knight, Gabi, Zarggg

Description

I cannot join any AIM chatroom (only at rare times) Either by accepting invitations or adding a chatroom then trying to join it, nothing happens. I'm on Windows XP SP2 and this error has been happening since GAIM 1.5 for me. I saw a related post on Digg about this problem, but I have not found any related reports on it.

Either way, this is annoying since my friend and I just make random chats, but most of the time I cannot join. When I do, after a while, when I make a message in the chatroom, it doesn't show up on the chat screen, but I'm still in the room, seeing incoming messages, while not being able to send any myself. That is when I have to try to rejoin the chat room (if I even can). I've had this issue without any plugins running and has been occuring since I've been using GAIM. I'm not sure if this occurs only on my computer, but I'll try on another.

Change History (56)

comment:1 Changed 12 years ago by lschiere

  • Component changed from pidgin (gtk) to libpurple
  • Milestone set to 2.1.2
  • Owner set to MarkDoliner

comment:2 Changed 12 years ago by MarkDoliner

Do you get an error message when unable to join? What about when in the chatroom but unable to send a message? Can you give some examples of the names of the rooms?

comment:3 Changed 12 years ago by Refinery

The names of the rooms are normal, either chat(random numbers) or a specific name such as "HW help chat". I cannot join when Pidgin is on for longer than a specific time. I noticed to get into the channel, I'd have to restart Pidgin, then join. Also, over a period of time in the channel, I get randomly kicked out, and I know I'm not passing the message limit in the room. I'd have to try to rejoin, and sometimes it doesn't let me. I can send messages when I'm in the room, and I do not get an error message. Accepting an invite doesn't let me enter, and neither does adding the chat to my list, then manually trying to join. It simply doesn't allow me to enter, and double clicking on the chat room does not do anything (such as open a new window).

comment:4 Changed 12 years ago by guyr

I just experienced this issue tonight. I was running 2.0.1, but upgraded to 2.0.2 to see if that would fix it. Unfortunately, it didn't. I ran the Gaim 2.0 betas ever since they were available and had no issues joining AIM chats. This is consistently repeatable for me. I can't initiate or join any AIM chat. I receive the invitations if others initiate, but accepting does nothing. Initiating a chat does nothing either. No errors are logged, unless I'm looking in the wrong place (Tools - System Log).

comment:5 Changed 12 years ago by MarkDoliner

Ok, I think I fixed this crash a day or two ago. The fix will make it into Pidgin 2.1.0, which should be released within the next two weeks.

I haven't been able to reproduce getting kicked out of a chat room though, and joining works for me 100% of the time, so it's hard for me to debug why that would happen.

comment:6 Changed 12 years ago by MarkDoliner

Oh, er, ignore the parts of my last comment about crashing, that was intended for a different bug report.

comment:7 Changed 12 years ago by guyr

I just discovered something that may or may not help someone identify this problem. On a second system still running GAIM 2.0 Beta 6, if I join a chat and type a small amount of jibberish as the chat room (e.g., "123q", it puts up an error messages saying "SNAC threw error: Busted SNAC payload". If I type a longer amount of jibberish for a chat room, it successfully starts a chat.

With Pidgin, if I do the same thing, in the first case it just doesn't appear to do anything. In the second case, it will successfully initiate a chat.

My original problem reported above is that I was attempting to join a valid chat room that a coworker had initiated, and Pidgin was silently failing.

comment:8 Changed 12 years ago by MarkDoliner

guyr: Oh, FYI Tools - System Log is the wrong place. If a message was printed somewhere it would be in the Debug Window, which is either in Help or Tools.

...and I still can't reproduce this.

comment:9 Changed 12 years ago by Vertelemming

I can confirm this bug myself, and have been having it since before the first beta of Gaim 2.0. As far as I've ever been able to tell, nothing shows up in the debug window after the initial request to join a chat room. I have noticed that closing Pidgin and restarting it allows me to chat for a while, but after an arbitrary amount of time (usually about half an hour), it kicks me out of any active chats and I'm unable to join any new chats.

I'm wondering if it might be something related to location, or network architecture. For as long as I've had this bug, I've been in the same town (Australia), and in the same sort of network (ADSL connection through a gateway router). Can't think of anything that would be that sensitive though.

I can confirm that chats in general do work, too; IRC works, as do MSN chats, and when I load Trillian, I can use AIM chats without a problem from there, so this is not something endemic to Pidgin in general.

comment:10 Changed 12 years ago by Vertelemming

Addendum to previous comment. I just had the bright idea (gosh, only now?) of trying Pidgin on one of the other computers in the house. Different OS, different version, same network and location, same problem. This heavily supports it being a bug with specific network configurations.

comment:11 Changed 12 years ago by guyr

MarkDoliner, thanks for pointing me to the correct place to look for the debug log. When I type "123q" as the chat room, I get

(12:00:42) oscar: Attempting to join chat room 123q. (12:00:42) oscar: chatnav exists, creating room (12:00:42) oscar: snac threw error (reason 0x000e: Busted SNAC payload)

which is the same message I saw in the popup under Gaim 2.0 Beta 6 on the other box. So the error is the same, and obviously not unique to any particular box. I'm running XP SP2 on both boxes. If I supply a longer chat room name, I get this:

(12:01:44) oscar: Attempting to join chat room weytrr5464767uyiyuh. (12:01:44) oscar: chatnav exists, creating room (12:01:44) oscar: created room: weytrr5464767uyiyuh 4 0 64 1185292904 2000 38 1 22 weytrr5464767uyiyuh aol://2719:10-4-weytrr5464767uyiyuh

comment:12 Changed 12 years ago by MarkDoliner

Oh, I see. You can't have a chat room that starts with a number. I'll work on improving our error handling in that case.

comment:13 Changed 12 years ago by nekid

I have had problems with chatting in Piding from the beginning, and I think they've gotten worse since I started using 2.1.0. Yesterday, I again randomly got kicked out of the chat, though I was still in it (I just couldn't send messages anymore). After that, I couldn't get into a chat again at all. I tried restarting Pidgin and my computer. Nothing. Here's what the debug window reports when I try to join a chat:

(11:45:49) oscar: Attempting to join chat room ICantChat!. (11:45:49) oscar: chatnav exists, creating room (11:45:49) oscar: snac threw error (reason 0x000e: Busted SNAC payload)

Okay, I just created a chat with all lowercase letters, and it worked. I'll posted again if/when I get kicked out of this chatroom.

comment:14 Changed 12 years ago by Niomar

I too have been experiencing this lately. However, I am rather confident this is due to a network configuration. Previously, I had no trouble with this, but then I upgraded my router to a WRT54GL with DD-WRT (v23 SP2) firmware. I am more than happy to provide any information to help resolve this, as it is very frustrating.

comment:15 Changed 12 years ago by Vertelemming

I think we have a commonality. I have a WRT54G, same DD-WRT firmware. Looks like we've found probable cause.

comment:16 Changed 12 years ago by MarkDoliner

Niomar and Vertelemming: Can you guys try editing your AIM account, go to the Advanced tab and set the server to "login.messaging.aol.com"?

comment:17 Changed 12 years ago by MarkDoliner

Niomar and Vertelemming: Actually, I have a feeling that won't help. But I'm wondering, do other AIM clients aside from Pidgin work behind your firewall?

comment:18 Changed 12 years ago by Vertelemming

Other AIM clients have always worked with me (see above: Trillian). Funny thing, but it looks like changing the server may be working. Will report back when I've been on AIM for 24+ hours, but it's been stable longer than ever so far.

comment:19 Changed 12 years ago by Niomar

Other AIM clients also work fine for me. I'll have to try the server modification within the next day or two. Last night, I updated my DD-WRT firmware to v23 SP3 (beta, dated 07/21/07) and my initial impression is that it did resolve the issue, but I wanted to test it some more tonight before confirming/posting on it.

comment:20 Changed 12 years ago by Vertelemming

Not very far off a full day on login.messaging.aol.com and AIM chats are still working. I sometimes have to try a few times before it'll let me into any given chat room, but it does let me in. And that's still using SP2 firmware. Weird.

comment:21 in reply to: ↑ description Changed 12 years ago by ewestland

Good morning,

I don't seem to be able to get a Yahoo or AOL chatrooms working (version 2.1.1 and 2.0.2). In early August, I was able to connect to Yahoo chatrooms, but now nothing happens. I can browse to the room (Tools -> roomlist -> My Yahoo Acct -> Get List -> Region -> US -> SF Bay Area -> "San Francisco Bay Area:100" -> Join. Nothing seems to happen. The log sometimes mentiones, "Writing file prefs.xml", but mentions nothing about the connection. The AOL connection seemed to try harder, but I get busted.

AOL (Soul and R&B:91 Exchange: 5) (02:50:50) oscar: creating room Soul and R&B:91 (02:50:50) oscar: snac threw error (reason 0x000e: Busted SNAC payload)

Yahoo ("San Francisco Bay Area:8") No debug info

I am running XP professional sp2 and using Belkin PreN router to front a Motorola cable modem. I have connected wireless/wired, to no avail.

Do chatrooms work reliably on Linux and/or Windows? I am planning to start tinkering with a utility using libpurple, but need chatroom support.

Thoughts?

Thanks in advance, Erik

comment:22 Changed 12 years ago by ewestland

BTW - I forgot to mention that both the Yahoo and AOL clients work behind my firewall.

Thanks for any insight....

comment:23 Changed 12 years ago by seanegan

  • Component changed from libpurple to AIM

comment:24 Changed 12 years ago by dave1g

tested this with 2.2.2, can get into a yahoo chat, but not aim, debug window says the same as ewestland

(00:50:18) oscar: Attempting to join chat room Soul and R&B:91.
(00:50:18) oscar: chatnav exists, creating room
(00:50:18) oscar: snac threw error (reason 0x000e: Busted SNAC payload)

when attempting to join a random chat room "testchat" I get a different debug log

(00:54:02) oscar: Attempting to join chat room testchat.
(00:54:02) oscar: chatnav exists, creating room
(00:54:02) oscar: created room: testchat 4 0 64 1193201643 2000 38 1 22 testchat !aol://2719:10-4-testchat
(00:54:02) oscar: snac threw error (reason 0x000d: Request denied)

comment:25 in reply to: ↑ description ; follow-up: Changed 12 years ago by bv1192

The same thing happens to me at work. It started happening, so i ran the debug window.

(10:16:25) oscar: Attempting to join chat room chatroom. (10:16:25) oscar: chatnav exists, creating room (10:16:25) Gtk: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (10:16:33) Gtk: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed (10:16:38) oscar: Attempting to join chat room chatroom. (10:16:38) oscar: chatnav exists, creating room

but nothing happens.

comment:26 Changed 11 years ago by guyr

Ugh, this is darn frustrating. I just installed the latest 2.2.2, and this is happening to me all the time now. If I start a chat, it shows nothing. If I accept an incoming invitation, nothing happens. I looked in the debug window, and it doesn't show any errors. It acknowledges my request to initiate chat "abc123", then says "opening chatnav window", then nothing.

I've got a work session tonight that I need to participate in, so I'm going to install Trillian. Ugh.

comment:27 Changed 11 years ago by dcarter

Similar problem, attempting to join a saved chat from buddy list produced the following debug and no chat window:

(16:55:54) oscar: Attempting to join chat room bcred.
(16:55:54) oscar: chatnav exists, creating room
(16:56:35) oscar: Scheduling destruction of FLAP connection of type 0x000d
(16:56:35) oscar: Destroying oscar connection of type 0x000d.  Disconnect reason is 4
(16:56:35) oscar: Disconnected.  Code is 0x0000 and msg is Windows socket error #10054
(16:57:08) oscar: Attempting to join chat room bcred.
(16:57:08) oscar: chatnav does not exist, opening chatnav
(16:59:05) oscar: unknown short capability: {010a}
(16:59:05) oscar: unknown short capability: {0107}
(16:59:05) oscar: unknown short capability: {0104}

*grovels before the mighty debug window*

comment:28 Changed 11 years ago by aquarichy

Hello. Trying to join an AIM Chat, no window ever opens. If a member tries to prompt me, I get the prompt, but accepting it, no chat window opens. Conversations with individuals will still get their own windows, just not group Chats.

In the debug window, I get:

(15:52:42) oscar: Attempting to join chat room avatarfans. (15:52:42) oscar: chatnav does not exist, opening chatnav

This is Pidgin 2.2.1 on Ubuntu 7.10.

What might be of great interest is that I can still join the above chatroom from my ICQ account. So, ICQ -> connects to chatroom, AIM -> no window appears.

This was using a fresh, clean installation of pidgin without any pre-existing .purple or .gaim directories lying around.

comment:29 in reply to: ↑ 25 Changed 11 years ago by bv1192

It happens with enough frequency that I can get a few grabs

(16:24:45) oscar: Attempting to join chat room bvschat.

(16:24:45) oscar: chatnav exists, creating room

(16:24:45) Gtk: gtk_entry_get_text: assertion `GTK_IS_ENTRY (entry)' failed

(16:24:46) util: Writing file prefs.xml to directory C:\Documents and Settings\BSullivan\Application Data\.purple

(16:24:46) util: Writing file C:\Documents and Settings\BSullivan\Application Data\.purple\prefs.xml

(16:24:55) oscar: Attempting to join chat room bvschat.

(16:24:55) oscar: chatnav exists, creating room

comment:30 follow-up: Changed 10 years ago by ticktock

I, along with a lot of my friends who use Pidgin (2.5.5), have been having the same problem and it's very frustrating. We'll get disconnected from an AIM chatroom or have an error where Pidgin will crash and when we try to log back into the room nothing happens. If one person remains in the room and another person who has this problem tries to restart Pidgin, the person still in the room will get the "XXX has left the room" message every time the other person exits the program without them ever having been able to rejoin the room to begin with.

When we get this error, we can't join ANY chat rooms - not just the one. But we are able to rejoin the same room (or any room) if we log on other screen names.

It happens seemingly randomly, and sometimes it just fixes itself, but we don't know why. Restarting the computer/router/modem does nothing.

This is the only thing that appears in the debug log on an unsuccessful attempt (standard login.messaging.aol.com for the server):

(23:42:53) oscar: Attempting to join chat room chaterror. 
(23:42:53) oscar: chatnav exists, creating room 
(23:42:55) oscar: created room: chaterror 4 0 64 1241926974 2000 39 1 22 chaterror aol://2719:10-4-chaterror

It says it created the room, yet no window pops up and anyone currently in the chatroom will not see us join.

on a successful attempt, we get something like this:

(00:09:53) oscar: Attempting to join chat room jonsucks. 
(00:09:53) oscar: chatnav exists, creating room 
(00:09:53) gtkappbar: wnd_poschanging 
(00:09:53) gtkappbar: wnd_poschanged 
(00:09:53) gtkappbar: wnd_activate 
(00:09:53) oscar: created room: jonsucks 4 0 64 1241928610 2000 39 1 22 jonsucks aol://2719:10-4-jonsucks 
(00:09:53) oscar: Connecting to FLAP server 205.188.179.20:5190 of type 0x000e (00:09:53) oscar: Connecting to chat room aol://2719:10-4-jonsucks exchange 4 (00:09:53) dnsquery: Performing DNS lookup for 205.188.179.20 
(00:09:53) dnsquery: IP resolved for 205.188.179.20 
(00:09:53) proxy: Attempting connection to 205.188.179.20 
(00:09:53) proxy: Connecting to 205.188.179.20:5190 with no proxy 
(00:09:53) proxy: Connection in progress 
(00:09:54) proxy: Connecting to 205.188.179.20:5190. 
(00:09:54) oscar: connected to FLAP server of type 0x000e 
(00:09:54) oscar: FLAP connection of type 0x000e is now fully connected 
(00:09:54) oscar: inside chat_info_update (maxmsglen = 2000, maxvislen = 1024) (00:09:55) util: Writing file prefs.xml to directory C:\Users\Mike\AppData?\Roaming\.purple 
(00:09:55) util: Writing file C:\Users\Mike\AppData?\Roaming\.purple\prefs.xml 
00:09:56) gtkappbar: wnd_activate

comment:31 Changed 10 years ago by rekkanoryo

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

comment:32 Changed 10 years ago by darkrain42

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

comment:33 Changed 10 years ago by darkrain42

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

comment:34 Changed 10 years ago by Daioh

It's great and all that the bug I reported is a 'duplicate of this bug', but for pete's sake, try to repair it. this bug had pidgin 2.1.2 as milestone to be fixed. we're at 2.5.8 and the problem still exists. At least update this bug properly to reflect reality.

Okay enough of my rant, time to add something constructive:

I only have the problem once I leave the chat for whatever reason (usually quite randomly). I did notice that it has become less and less problematic with the later versions though. The random disconnects appear less often and after a restart of pidgin I can usually join once again.

comment:35 Changed 10 years ago by SamuelRiv

I have been experiencing this problem (Win XP SP2, Pidgin 2.6.2, simple home wireless network) in which I would suddenly not be able to join AIM chat and with no visible error messages for the rest of an online session. I found that a basic ipconfig /flushdns entry in the command prompt was enough to get it working without having to restart Pidgin or the network connection. I would have to verify this fix more times, but maybe it will help those developers working on the problem.

comment:36 Changed 9 years ago by Rui

I have this problem, now, too. It's really strange. Earlier today, it was fine, though sometimes I would leave my computer, causing it to go to sleep and lose connection, and forcing me to restart Pidgin. However, suddenly, one time when I woke up my computer and restarted Pidgin and tried to join a chat room, nothing. I tried a few more times. Nothing. I restarted, then I shut off my computer for maybe 20 seconds or more, and when all else failed, I updated from 2.6.3 to 2.6.4. It still doesn't work.

Pidgin Debug Log : 12/6/2009 9:04:21 PM
(21:03:18) Gtk: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
(21:03:23) oscar: Attempting to join chat room facilitychat.
(21:03:23) oscar: chatnav exists, creating room
(21:03:28) util: Writing file blist.xml to directory C:\Users\Christina\AppData\Roaming\.purple
(21:03:28) util: Writing file C:\Users\Christina\AppData\Roaming\.purple\blist.xml
(21:03:44) oscar: Scheduling destruction of FLAP connection of type 0x000d
(21:03:44) oscar: Destroying oscar connection of type 0x000d.  Disconnect reason is 4
(21:03:44) oscar: Disconnected.  Code is 0x0000 and msg is Connection interrupted by other software on your computer.

The only other software I have running on my computer, besides my background stuff that I don't even know about, is Firefox 3.5.5 and Windows Live Messenger. I always ran these programs with them before, and I haven't had this trouble until tonight.

And the chat name, by the way, is all lowercase letters, with no spaces or anything like that.

comment:37 follow-up: Changed 9 years ago by yvh11a

Still occurs for me in Pidgin 2.6.4-1.fc11 (libpurple 2.6.4)

Can sometimes be fixed by disabling the account and then re-enabling.

comment:38 in reply to: ↑ 37 Changed 9 years ago by yvh11a

Replying to yvh11a:

Still occurs for me in Pidgin 2.6.4-1.fc11 (libpurple 2.6.4)

Can sometimes be fixed by disabling the account and then re-enabling.

Sorry to double-post. Just noticed something possibly interesting. If you close the chat before you're kicked by the server, you don't have to disable the account, you can simply rejoin. If you get kicked by the server, you have to disable and re-enable.

Here's how to duplicate it:

  1. Join a chat room with Pidgin. Also join the same chat room using a different client and a different account (I'm using Naim). Make sure there's traffic in the room.
  1. When things are working, you'll get messages to both windows, Pidgin and Naim. When Pidgin dies, you'll see messages arriving in Naim, but not in Pidgin. At this time, if you close the chat tab, you can rejoin the room with the "Join chat" command or by clicking on a saved chat in the buddy list, as normal.
  1. If you leave the tab open long enough, Naim will show that your Pidgin account has left the room. After this point, you can't get Pidgin to re-join the room, even if you close the tab, and an account disable-reenable is required to get chat functionality back.

Hope this helps.

comment:39 Changed 9 years ago by Jade Knight

Still occurs with Pidgin 2.6.6.

I don't tend to get randomly kicked from chats, but I occasionally find myself unable to join them.

Random peculiarities: I am sometimes able to join a DIFFERENT chat while remaining locked out of one, but not always. I am usually able to join chats with different accounts also logged into Pidgin (I don't have to use a different client). When I have one account in the room, and the other tries to join, all you get is the "left the room" message.

When trying to join a chat unsuccessfully, this is what goes in the debug window: (09:21:28) oscar: Attempting to join chat room arena. (09:21:28) oscar: chatnav exists, creating room (09:21:28) oscar: created room: arena 16 0 64 1266600080 2000 50 1 22 arena aol://2719:10-16-arena

And that's it. I get no message of any sort. It just won't join. Invitations don't help.

Disabling the affected account and reenabling does not fix this problem for me. Closing Pidgin entirely and then reopening it does not fix this problem for me. I don't know what causes the problem, and I don't know how to work around it except to use a different SN whenever one can't get into a chatroom.

I've tried signing off the problematic account in Pidgin and then signing on in Meebo once, and then inviting it to a chatroom, and the problem persists (or did the one time I tried this).

This may suggest that the issue is related directly to the way the protocol handles things, but is there any way to work around this without switching SN's?

comment:40 Changed 9 years ago by rekkanoryo

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

comment:41 Changed 9 years ago by rekkanoryo

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

comment:42 follow-up: Changed 9 years ago by jarome

This is happening to me a lot lately using Adium 1.4b17 Even if I use AIM chat rooms that I saved, I never enter them. And I can't accept invites from others. It is getting really frustrating. And in Yahoo chats, if I am not the last person in the room, I often cannot see what some people are typing.

comment:43 in reply to: ↑ 42 Changed 9 years ago by Gabi

I'm using version 2.6.4 for Debian and I cannot create nor join any AIM chatrooms. If I add the chatroom to my buddy list, I am sometimes able to join it, but not always. And I'm not getting any error messages when I cannot join, nothing happens.

Even when I can join, I cannot see other people who have joined after me. If I disconnect and reconnect, then I can see them (but then they have not joined after me anymore).

comment:44 Changed 9 years ago by Zarggg

Confirming bug still exists as of 2.7.2 Windows.

I was able to create and join the chat, but after leaving it, all attempts to join give the follow debug messages:

(19:46:10) oscar: Attempting to join chat room Mystery Heroes Council.
(19:46:10) oscar: chatnav exists, creating room
(19:46:10) oscar: created room: Mystery Heroes Council 4 0 64 1281311170 2000 39 1 22 Mystery Heroes Council !aol://2719:10-4-mysteryheroescouncil

Being invited generates the following debug messages:

(19:47:50) oscar: Incoming rendezvous message of type 8, user x0x thinkofme, status 0
(19:47:50) oscar: Empty encoding, assuming UTF-8
(19:47:55) oscar: Attempting to join chat room mysteryheroescouncil.
(19:47:55) oscar: chatnav exists, creating room
(19:47:55) oscar: created room: mysteryheroescouncil 4 0 64 1281311275 2000 39 1 22 mysteryheroescouncil !aol://2719:10-4-mysteryheroescouncil

Neither actually opens the chat window.

comment:45 in reply to: ↑ description ; follow-up: Changed 9 years ago by Ghostbeef

Confirming the same as above, and that it's got to be related with the network used. I had to install a new router after the last one got damaged by lightning, and now I encounter the problem described.

When I send a message through a chat window, it doesn't show up at once and either I get the error message "You have been disconnected from chat room aol://2719:10-4-sfcchat." without my message ever showing up for me (people in the room sometimes see my message), or I get the messages that have been sent by other people all at once, plus my message under them, all with the same timestamp (then I'm still in the room).

If I do nothing, I get no error message but people in the room see me leave at some point. And if I somehow manage to stay in the room longer than several minutes, I'm suddenly kicked out with the error message. No delay.

AIM chatrooms used to work just fine before the router change.

I tried to forward the AIM chat port, but no luck. Here's what my debug window says when:

  • I'm kicked out after sending a message that doesn't show up:

(12:06:54) oscar: Scheduling destruction of FLAP connection of type 0x000e (12:06:54) oscar: Destroying oscar connection of type 0x000e. Disconnect reason is 2 (12:06:54) oscar: Disconnected. Code is 0x0000 and msg is (12:06:54) server: Leaving room: sfcchat

  • attempting to go back in the room without:

(12:09:31) oscar: Attempting to join chat room sfcchat. (12:09:31) oscar: chatnav exists, creating room (12:10:36) oscar: Scheduling destruction of FLAP connection of type 0x000d (12:10:36) oscar: Destroying oscar connection of type 0x000d. Disconnect reason is 4 (12:10:36) oscar: Disconnected. Code is 0x0000 and msg is Connection interrupted by other software on your computer.

My new router is a Livebox 2 mini (Sagem).

comment:46 in reply to: ↑ 30 Changed 9 years ago by VulpesFoxnik

Replying to ticktock:

I, along with a lot of my friends who use Pidgin (2.5.5), have been having the same problem and it's very frustrating. We'll get disconnected from an AIM chatroom or have an error where Pidgin will crash and when we try to log back into the room nothing happens. If one person remains in the room and another person who has this problem tries to restart Pidgin, the person still in the room will get the "XXX has left the room" message every time the other person exits the program without them ever having been able to rejoin the room to begin with.

When we get this error, we can't join ANY chat rooms - not just the one. But we are able to rejoin the same room (or any room) if we log on other screen names.

It happens seemingly randomly, and sometimes it just fixes itself, but we don't know why. Restarting the computer/router/modem does nothing.

This is the only thing that appears in the debug log on an unsuccessful attempt (standard login.messaging.aol.com for the server):

(23:42:53) oscar: Attempting to join chat room chaterror. 
(23:42:53) oscar: chatnav exists, creating room 
(23:42:55) oscar: created room: chaterror 4 0 64 1241926974 2000 39 1 22 chaterror aol://2719:10-4-chaterror

It says it created the room, yet no window pops up and anyone currently in the chatroom will not see us join.

on a successful attempt, we get something like this:

(00:09:53) oscar: Attempting to join chat room jonsucks. 
(00:09:53) oscar: chatnav exists, creating room 
(00:09:53) gtkappbar: wnd_poschanging 
(00:09:53) gtkappbar: wnd_poschanged 
(00:09:53) gtkappbar: wnd_activate 
(00:09:53) oscar: created room: jonsucks 4 0 64 1241928610 2000 39 1 22 jonsucks aol://2719:10-4-jonsucks 
(00:09:53) oscar: Connecting to FLAP server 205.188.179.20:5190 of type 0x000e (00:09:53) oscar: Connecting to chat room aol://2719:10-4-jonsucks exchange 4 (00:09:53) dnsquery: Performing DNS lookup for 205.188.179.20 
(00:09:53) dnsquery: IP resolved for 205.188.179.20 
(00:09:53) proxy: Attempting connection to 205.188.179.20 
(00:09:53) proxy: Connecting to 205.188.179.20:5190 with no proxy 
(00:09:53) proxy: Connection in progress 
(00:09:54) proxy: Connecting to 205.188.179.20:5190. 
(00:09:54) oscar: connected to FLAP server of type 0x000e 
(00:09:54) oscar: FLAP connection of type 0x000e is now fully connected 
(00:09:54) oscar: inside chat_info_update (maxmsglen = 2000, maxvislen = 1024) (00:09:55) util: Writing file prefs.xml to directory C:\Users\Mike\AppData?\Roaming\.purple 
(00:09:55) util: Writing file C:\Users\Mike\AppData?\Roaming\.purple\prefs.xml 
00:09:56) gtkappbar: wnd_activate

I can confirm that these symptoms also Exist in Debian 2.7.2

comment:47 Changed 8 years ago by nrsidavidr

I've been having similar problems of being disconnected from an AIM chatroom and then unable to rejoin it. I get

13:58:01) util: Writing file C:\Users\Da\AppData?\Roaming\.purple\blist.xml (13:58:01) util: Writing file prefs.xml to directory C:\Users\Da\AppData?\Roaming\.purple (13:58:01) util: Writing file C:\Users\Da\AppData?\Roaming\.purple\prefs.xml (13:58:05) g_log: purple_blist_node_get_string: assertion `purple_value_get_type(value) == PURPLE_TYPE_STRING' failed (13:58:06) oscar: Attempting to join chat room (chat room name). (13:58:06) oscar: chatnav exists, creating room (13:58:06) oscar: created room: (chat room name) 4 0 64 1297346280 2000 39 1 22 (chat room name) aol://2719:10-4-(chat room name) (13:58:11) oscar: Attempting to join chat room (chat room name). (13:58:11) oscar: chatnav exists, creating room (13:58:11) oscar: created room: (chat room name) 4 0 64 1297346285 2000 39 1 22 (chat room name) aol://2719:10-4-(chat room name)

in the debug log. This is with pidgin 2.7.9 on one system and 2.7.6 on another. Rebooting does _not_ resolve the problem.

comment:48 Changed 8 years ago by nrsidavidr

I've investigated further and, when I get to the state I can't join the chatroom, simply right-clicking on the chatroom within my buddies list gives

(09:26:22) g_log: purple_blist_node_get_string: assertion purple_value_get_type(value) == PURPLE_TYPE_STRING' failed

This is just as described in Ticket #10429. The problem usually resolves itself, sometimes after several hours.

comment:49 Changed 8 years ago by MarkDoliner

I think the warning "purple_blist_node_get_string: assertion purple_value_get_type(value) == PURPLE_TYPE_STRING' failed" is totally harmless and unrelated to this problem. FYI I just committed e4546fa88606ad39b1926afe342cdda4b92a2451 that should eliminate it.

comment:50 Changed 8 years ago by MarkDoliner

I was able to reproduce this just now, and I had wireshark running and capturing packets. Pidgin sends the 0x0d/0x08 SNAC to the chatnav server to attempt to create a new room, but we don't get any response from the server. My computer tries to retransmit the request after 0.6s, then again after 1.2s, then 2.4s, 4.8s, 9.6s, 19.2s, etc.

I'm not sure why my computer never gives up and realizes that the transmission is failing. The most recent request before my create request was 952s earlier. It was successful, and there were no other TCP messages between those two events.

I don't know if this problem lies in my router, or if AOL's servers aren't sending a TCP failure messages when we expect them to. I might experiment with sending some sort of keepalive message on chat and chatnav connections.

comment:51 Changed 8 years ago by MarkDoliner

Looks like the current version of the Windows AIM clients sends some sort of keepalive every 178 or 179 seconds. Pidgin only sends keepalives on the primary FLAP connection. We should probably send keepalives on all FLAP connections.

If anyone compiles Pidgin themselves and wants to test, you could try this patch:

============================================================
--- libpurple/protocols/oscar/oscar.c	d2c9d3d86e975571c10f6163835a48696e3e2b81
+++ libpurple/protocols/oscar/oscar.c	1832433d5ba5e7cffb9ef3f207f2af3281d3d32e
@@ -3140,12 +3140,12 @@ oscar_keepalive(PurpleConnection *gc)
 oscar_keepalive(PurpleConnection *gc)
 {
 	OscarData *od;
-	FlapConnection *conn;
+	GSList *l;
 
 	od = purple_connection_get_protocol_data(gc);
-	conn = flap_connection_getbytype(od, SNAC_FAMILY_LOCATE);
-	if (conn != NULL)
-		flap_connection_send_keepalive(od, conn);
+	for (l = od->oscar_connections; l; l = l->next) {
+		flap_connection_send_keepalive(od, l->data);
+	}
 }
 
 unsigned int

comment:52 in reply to: ↑ 45 Changed 8 years ago by Ghostbeef

Just dropping by to say that I have exchanged my router at my ISP again for an upgraded version. This new one fixes the problem I described a few replies back.

comment:53 Changed 8 years ago by nrsidavidr

Thanks for looking into this. The problems I've been seeing don't seem to fit with it being a keepalive problem. On several occasions, when I've been in the state of being unable to connect to a chat room, rebooting the computer, or switching to a different computer has not resolved the problem. So any old tcp/ip connections would have gone. On one occasion I also restarted my internet router to no avail.

comment:54 Changed 8 years ago by MarkDoliner

nrsidavidr: When you get into that state... are you able to join chat rooms if you log into AIM using an official AIM program?

comment:55 Changed 8 years ago by markdoliner@…

  • Milestone set to 2.7.11
  • Resolution set to fixed
  • Status changed from new to closed

(In 81c3582e4a36c00dd7c62683f83fcb114b07ae85):
Send keepalives for all types of network connections. Will hopefully make chat rooms more reliable. Fixes #1449

comment:56 Changed 8 years ago by nrsidavidr

Mark - Thanks for the suggestion. I've not got the official AIM program installed at present, but I'll do that when I get a chance, test and report back. You've made me think that my symptoms do seem to point to a problem at the end rather than client. I've not actually had the problem recently, so may be a while before I can test...

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!