Opened 12 years ago

Last modified 3 years ago

#3697 new defect

Unable To Add: Could not add the buddy 1 for an unknown reason.

Reported by: ianzabel Owned by: MarkDoliner
Milestone: Component: AIM
Version: 2.2.2 Keywords: aim, unable, buddy list, unknown
Cc: CookieOfFortune, kel, dygituljunky, BWJM

Description

Every time I sign in to AIM, I get an error saying:

Unable To Add
Could not add the buddy 1 for an unknown reason

This seems to be different than #577 because I do not see the full error message noted in that bug.

I have 184 buddies on my list, so it's not full. When I sign into my AIM account using AOL Instant Messenger or Meebo, I do not see any errors or messages about buddies waiting to be added or anything.

The only thing that looks like it could be related in the debug log during login is this:

(10:38:55) oscar: ssi: status is 0x000a for a 0x0008 action with name no item
(10:38:55) oscar: ssi: Action 0x0008 was unsuccessful with error 0x000a

Change History (83)

comment:1 Changed 11 years ago by ianzabel

I recently added ICQ to my accounts, and I get the same error dialog when signing in:

Unable To Add
Could not add the buddy 1 for an unknown reason

I see this in the debug log:

(10:03:30) oscar: ssi: status is 0x0000 for a 0x0008 action with name no name
(10:03:30) oscar: ssi: status is 0x0001 for a 0x0008 action with name no item
(10:03:30) oscar: ssi: Action 0x0008 was unsuccessful with error 0x0001
(10:03:30) oscar: icq response: 11 bytes, 4758962, 0x07da, 0x0015

So, now when I sign in to Pidgin, I get two "Unable To Add" alerts: one for AIM, one for ICQ.

This is Pidgin 2.3.0.

comment:2 follow-up: Changed 11 years ago by Sim-on

  • pending changed from 0 to 1

Does this still happen in 2.4.0 ?

comment:3 in reply to: ↑ 2 Changed 11 years ago by ianzabel

  • pending changed from 1 to 0

Replying to Sim-on:

Does this still happen in 2.4.0 ?

Yes, same behavior in 2.4.0.

comment:4 Changed 11 years ago by jhnphm

I still get this w/ 2.4.1 on Ubuntu Hardy. I get the same error posted above in the debug logs, and it appears to be account-specific, as it does not affect my other AIM accounts. I've tried removing everyone and re-adding, w/ no success.

comment:5 Changed 11 years ago by ianzabel

Behavior still exists in 2.4.2 on windows.

comment:6 in reply to: ↑ description Changed 11 years ago by m1ss1ontomars2k4

Yep, this is still the case.

As a matter of fact, I now get two of these messages (identical).

Adium now suppresses these messages, as no one understands what they mean or what they're good for.

comment:7 Changed 11 years ago by HaMF

Still exists in 2.4.3. Why don't treat the error message as adium does? (Just ignore/surpesss it?)

comment:8 Changed 11 years ago by protocol

It has to do with either the login or parsing the buddy list or something. Still an issue in newest 2.4.3 as stated above...

comment:9 Changed 11 years ago by protocol

Possibly it is parsing the buddy list with .. and if people have a elipse or dots in their status like "blah blah blah that sucks..." then maybe that is throwing the parsing off?

comment:10 Changed 11 years ago by protocol

I FOUND THE SOLUTION TO THIS PROBLEM!!!

I decided to try Trillian to see if I got a similar error, well while looking through all the options I noticed a LARGE number of names in the ignore list. I cleared the list and ran Pidgin again and no more error!!!!

comment:11 Changed 11 years ago by HaMF

I just downloaded, emulated and set up trillian, connected to ICQ once and disconnected again. Result: The error's gone.* Trillian is obviousely able to fix the buddylist or whatever causes the error.

This does not make the bug of pidgin less important but at least I know what I have to do next time the alert shows up. (Download and emulate a proprietary program designed for windows.)

*No messing with the ignore list necessary. Mine is empty after all.

PS: Preview of comments does not work btw.

comment:12 Changed 11 years ago by ianzabel

I am no longer getting this error in 2.5.0. I haven't changed anything on my end, as far as I know; also have not logged into AIM with any other clients.

comment:13 Changed 11 years ago by jhnphm

Still getting it on 2.5.0 on Ubuntu. Since it doesn't seem to do anything, why not suppress it?

comment:14 Changed 10 years ago by rekkanoryo

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

comment:15 Changed 10 years ago by CookieOfFortune

2.5.5 on Windows with this error. Recently, it has been popping up constantly (every second or two) to the point that Pidgin is not usable.

comment:16 Changed 10 years ago by datallah

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

comment:17 Changed 10 years ago by datallah

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

comment:18 Changed 10 years ago by kel

Hello, I have the win32 client of Pidgin 2.5.5 on Vista and after logging on I receive about 28 pop ups in a row that say "Could not add the buddy 1 for an unknown reason."

A couple weeks ago it was only One pop up when signing on. It has been for some time now I'd say a couple years Now it happens about ten seconds or so. This issue only happens with one of two AIM accounts.

The same exact issue happens on Ubuntu also. It does not happen with the AIM Client, Tillian, or Meebo. So I beleive the issue may be server side.

Is there some server error that pidgin is reporting that it shouldn't be?

comment:19 Changed 10 years ago by m1ss1ontomars2k4

OK, seriously, we have neither cause nor effect for this--all we get is a meaningless message that annoys everyone. We can make this bug go away very easily by simply suppressing the message--why hasn't that been done yet?

comment:20 Changed 10 years ago by CookieOfFortune

You can load your buddy list in Trillian and it will fix the issue. This isn't a real fix though, because Pidgin shouldn't be generating the error like that to begin with.

comment:21 Changed 10 years ago by kelbizzle

I've signed onto Trillian Pro V 3.1.12.0. The same issue happens. I don't recall ever adding a buddy with screen name of 1. Hmm...I wonder what has changed.

comment:22 follow-up: Changed 10 years ago by kelbizzle

I just downloaded and reinstalled Trillian Basic 3.1.

I signed on using Trillian. Then signed on from pidgin at the same time. I noticed I did not get the popups. I signed off Trillian and Pidgin, then back onto Pidgin and now the issue it gone!

comment:23 in reply to: ↑ 22 Changed 10 years ago by charmedguy18

Replying to kelbizzle:

I just downloaded and reinstalled Trillian Basic 3.1.

I signed on using Trillian. Then signed on from pidgin at the same time. I noticed I did not get the popups. I signed off Trillian and Pidgin, then back onto Pidgin and now the issue it gone!

This works. It seems like a hassle, but it only takes the one time. 1) Make sure you're actually having this problem (duh) 2) Download Trillion. 3) Put in your AIM information and log into Trillion Basic. 4) At this point, DO NOT sign off of AIM from Trillion OR close it. Open Pidgin and let it sign on to AIM. 5) Close Trillian and Pidgin. 6) Sign back onto Pidgin and the problem should be completely gone. You won't have to repeat this again.

comment:24 follow-ups: Changed 10 years ago by CookieOfFortune

Does anyone know how to recreate this issue? I'll look at the code and try to find a solution when I have time. It really shouldn't depend on another program to fix this.

comment:25 in reply to: ↑ 24 Changed 10 years ago by charmedguy18

Replying to CookieOfFortune:

Does anyone know how to recreate this issue? I'll look at the code and try to find a solution when I have time. It really shouldn't depend on another program to fix this.

I agree, it shouldn't. But the only way I'd know to recreate the issue is to simply use a program to completely uninstall Pidgin and then re-install it. This issue happened my first time I opened Pidigin with AIM. So, it wasn't hard for me to re-create... But as soon as I did that thing with Trillion, it started working like nothing was wrong...

comment:26 in reply to: ↑ 24 Changed 10 years ago by charmedguy18

Replying to CookieOfFortune:

Does anyone know how to recreate this issue? I'll look at the code and try to find a solution when I have time. It really shouldn't depend on another program to fix this.


I agree, it shouldn't. But the only way I'd know to recreate the issue is to simply use a program to completely uninstall Pidgin and then re-install it. This issue happened my first time I opened Pidigin with AIM. So, it wasn't hard for me to re-create... But as soon as I did that thing with Trillion, it started working like nothing was wrong...
Sorry about the repost, I'm getting used to this new type of thread-type. I reposted to make it easier to understand, ahaha

comment:27 Changed 10 years ago by dygituljunky

This issue is still occurring with Pidgin 2.5.6.

comment:28 Changed 10 years ago by louipc

Silly. protocol mentioned the ignore list in Trillian. That should have given someone a clue.

The workaround in pidgin is to edit your block lists via the Tools > Privacy menu.

I'd be nice if unblocking automatically corrected the lists though.

comment:29 Changed 9 years ago by lvd

I'm on the ICQ network with the Windows client and I had the "unable to add .." error for some time now. After some reading I tried the Trillian solution and seems to work for me too.

However on an additional note, immediately after connecting to my account with Trillian, I noticed that an Umlaut of one of my buddies was garbled - it was an ö. I changed that to an oe and the unable to add error in Pidgin disappeared.

It also seems that Pidgin automatically translates oe to ö, as my buddy's name didn't change.

Maybe this error message has something to do with http://developer.pidgin.im/ticket/1645

comment:30 Changed 9 years ago by spledger

Hey all, I'm getting this with all 3 of my AIM accounts on Ubuntu 8.04 with 2.6.6 installed. Very annoying when it pops up not one but several hundred times. Is there any workaround other than using Trillian? I'd much rather not install it for just one use.

comment:31 Changed 9 years ago by bannah508

i am getting the same problem, i now have 249 and growing windows popping up that say can not add the buddy 1. i do not know what is going on. need this fixed now. please help.

comment:32 follow-ups: Changed 9 years ago by kalir

I believe this is a network problem as I know others who have blank buddy lists in AIM's provided client upon logging in. But I too can confirm this issue. Pidgin 2.7.0-2.fc11.

comment:33 in reply to: ↑ 32 Changed 9 years ago by kalir

Replying to kalir:

I believe this is a network problem as I know others who have blank buddy lists in AIM's provided client upon logging in. But I too can confirm this issue. Pidgin 2.7.0-2.fc11.

Erm, whereby network I mean server. Sorry for the ambiguity.

comment:34 in reply to: ↑ 32 Changed 9 years ago by madlordofmilk

Replying to kalir:

I believe this is a network problem as I know others who have blank buddy lists in AIM's provided client upon logging in. But I too can confirm this issue. Pidgin 2.7.0-2.fc11.

I have exactly that problem. Pidgin now spams that message to me, and my buddy list is empty in AIM, Trillian, and Meebo... d'oh.

comment:35 Changed 9 years ago by MarkDoliner

To anyone who sees this dialog opening many times: What version of Pidgin are you using?

comment:36 follow-up: Changed 9 years ago by eitan1989

This must be a very recent server problem as we've all started having it in the last half hour - I'm getting quite a few of them also - version 2.6.6.

comment:37 in reply to: ↑ 36 ; follow-ups: Changed 9 years ago by eitan1989

... and it's magically resolved itself. I guess they fixed the server.

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

Replying to eitan1989:

... and it's magically resolved itself. I guess they fixed the server.

Agreed. Seems to be working correctly for now.

comment:39 in reply to: ↑ 37 Changed 9 years ago by Miraxis

Replying to eitan1989:

... and it's magically resolved itself. I guess they fixed the server.

Was having the same issue with client v2.7.1, now it seems to be working normally.

comment:40 follow-ups: Changed 9 years ago by MarkDoliner

Buddy "1" is your buddy icon. So Pidgin was unable to set your icon.

In this case it seems like some group of servers at AOL was inaccessible, so we were either unable to connect or unable to issue a certain request. And apparently we sometimes issue that request in a loop. We definitely shouldn't show that error to the user more than once. We probably shouldn't show it even the first time.

comment:41 in reply to: ↑ 40 Changed 9 years ago by kalir

Replying to MarkDoliner:

Buddy "1" is your buddy icon. So Pidgin was unable to set your icon.

In this case it seems like some group of servers at AOL was inaccessible, so we were either unable to connect or unable to issue a certain request. And apparently we sometimes issue that request in a loop. We definitely shouldn't show that error to the user more than once. We probably shouldn't show it even the first time.

Sure, but the buddy list was blank for me on Pidgin, and for others who used AIM. Would an inability to set the buddy icon prevent the buddy list from being populated? Incidentally, it seemed that IMs could be exchanged if you knew the person's SN, as I received an IM on a name I was already signed into (and thus had a list and no errors), from someone using AIM that had just signed on, without a list.

comment:42 Changed 9 years ago by MarkDoliner

One part of the protocol that deals with storing buddy icons utilizes the same storage servers as the buddy list. I don't think an inability to set a buddy icon would cause the buddy list to not be populated, but both problems could be caused by servers being down on AOL's end.

comment:43 in reply to: ↑ 40 Changed 9 years ago by spledger

Replying to MarkDoliner:

Buddy "1" is your buddy icon. So Pidgin was unable to set your icon.

In this case it seems like some group of servers at AOL was inaccessible, so we were either unable to connect or unable to issue a certain request. And apparently we sometimes issue that request in a loop. We definitely shouldn't show that error to the user more than once. We probably shouldn't show it even the first time.

I definitely agree. My laptop was having difficulties with the 342 windows that popped up (Compiz can be a major pain sometimes lol).

comment:44 follow-up: Changed 9 years ago by MarkDoliner

Another question for people who saw this dialog opening many times: Did you have a buddy icon set? (either specifically for that account, or globally for all your accounts)

comment:45 Changed 9 years ago by Adhemar

I'm still having this problem now. Disabling all buddy icons doesn't help.

comment:46 Changed 9 years ago by kc8tpz

I had no icons set, globally or otherwise. I'm also having the issue now, pops up many times and continues to pop up until I disable the account. I'm running 2.7.1 on Win7.

comment:47 Changed 9 years ago by Adhemar

Yeah, 2.7.1 on Windows 7 here too.

comment:48 Changed 9 years ago by BWJM

Windows XP, Pidgin 2.7.1. Happening for me too.

comment:49 Changed 9 years ago by imjoshsizemore

I got multiple windows as well. I didn't have a buddy icon. I added a buddy icon and now I just get one window but buddy is is still empty.

comment:50 Changed 9 years ago by kc8tpz

I'm seeing something a bit different in my log than mentioned:

...
(20:04:49) nss: Handshake failed  (-5961)
(20:14:53) oscar: unable to connect to FLAP server of type 0x0018
(20:14:53) oscar: Scheduling destruction of FLAP connection of type 0x0018
(20:14:53) oscar: Destroying oscar connection of type 0x0018.  Disconnect reason is 6
(20:14:53) oscar: Disconnected.  Code is 0x0000 and msg is SSL Handshake Failed
(20:14:53) oscar: ssi: status is 0x0001 for a 0x0008 action with name no item
(20:04:49) oscar: ssi: Action 0x0008 was unsuccessful with error 0x0001
...
(20:14:53) oscar: FLAP connection of type 0x000d is now fully connected
(20:14:54) oscar: ssi: status is 0x0001 for a 0x0008 action with name no item
(20:14:54) oscar: ssi: Action 0x0008 was unsuccessful with error 0x0001
(20:14:54) oscar: ssi: status is 0x000d for a 0x0008 action with name no item
(20:14:54) oscar: ssi: Action 0x0008 was unsuccessful with error 0x000d

These messages repeat again and again. It looks almost like an SSL issue, but I tried deleting my cached certificates already.

comment:51 follow-up: Changed 9 years ago by MarkDoliner

People who see many many dialogs: Does your buddy list load?

comment:52 Changed 9 years ago by imjoshsizemore

When I saw many dialogs my list did not load

comment:53 follow-up: Changed 9 years ago by Adhemar

My list did load.

comment:54 in reply to: ↑ 51 Changed 9 years ago by kc8tpz

Replying to MarkDoliner:

People who see many many dialogs: Does your buddy list load?

Mine didn't.

comment:55 in reply to: ↑ 53 ; follow-up: Changed 9 years ago by shadus

Replying to Adhemar:

My list did load.

I get about 40-50 windows coming up with the message "Unable to add Buddy 1 for an unknown reason." Then a new window comes up like that every 5-8s until I disable the AIM account. My buddy list DOES load and it shows both offline and online users in the appropriate modes... but the messages keep rolling in. I only have maybe 50-60 people total on my list... looks like I might be getting 1 box per person who is offline maybe?

comment:56 Changed 9 years ago by Adhemar

Upon further inspection; the buddies that do load are from other protocols. The AIM ones don't appear.

comment:57 in reply to: ↑ 55 ; follow-up: Changed 9 years ago by shadus

Replying to shadus:

I get about 40-50 windows coming up with the message "Unable to add Buddy 1 for an unknown reason." Then a new window comes up like that every 5-8s until I disable the AIM account. My buddy list DOES load and it shows both offline and online users in the appropriate modes... but the messages keep rolling in. I only have maybe 50-60 people total on my list... looks like I might be getting 1 box per person who is offline maybe?

I stand corrected, reloaded it just now and buddy list is dead empty. Also empty on the normal aim express client as well as the full standard aim client. Meh.

comment:58 in reply to: ↑ 57 Changed 9 years ago by kc8tpz

Replying to shadus:

Replying to shadus:

I get about 40-50 windows coming up with the message "Unable to add Buddy 1 for an unknown reason." Then a new window comes up like that every 5-8s until I disable the AIM account. My buddy list DOES load and it shows both offline and online users in the appropriate modes... but the messages keep rolling in. I only have maybe 50-60 people total on my list... looks like I might be getting 1 box per person who is offline maybe?

I stand corrected, reloaded it just now and buddy list is dead empty. Also empty on the normal aim express client as well as the full standard aim client. Meh.

And in Miranda (tried with and without SSL) and in Meebo. Problem appears to be AOL fail.

comment:59 in reply to: ↑ description Changed 9 years ago by captbeagle

I've never had this problem before, but started having it today. Updated to 2.7.1 and when the AIM plugin is enabled, I get about 60 dialogs (and they just keep on coming until I disable the plugin again) over the course of half a minute or so. My buddy list is completely empty and I've never set a buddy icon for the account before.

comment:60 Changed 9 years ago by gleaken

I can confirm that it is AOL specific and the buddy list does not load. This is on Ubuntu 8.10 Pidgin 2.7.1. Web based AIM also does not list buddy list. I can confirm that when logged in via the web, you can communicate with buddies, they do not show up on your list. Some accounts with a few contacts can connect without error and show buddies in pidgin and others cannot. Any buddy with a significant amount of buddies shows no buddies and displays the dialog box with "Could not add..."

comment:61 Changed 9 years ago by SilverSeraphim

I too am having this issue. Everything worked fine at work today, but when I logged on at home I get numerous "Unable to add..." alerts and the buddy list is empty.

Logging on to AIM via AIM Express or Trillian doesn't show the alerts, but the buddy list is still empty.

comment:62 Changed 9 years ago by davodavo

Same issue on WinXP SP3 with Pidgin 2.7.1. Did reboot and reinstall. Changed protocol parameters (SSL on/off, proxy on/off). Tried it on three separate AOL accounts. All the same stuff. Buddy list loads for all other protocols, but not AOL.

comment:63 Changed 9 years ago by dtfinch

Same here on Ubuntu 10.04 (repository has only Pidgin 2.6.6). Started this evening. Several of these popups opened per second until I closed Pidgin. Never happened before.

Restarting Pidgin seemed to fix it for now. And unlike others, I haven't noticed anyone missing from my buddy list yet.

comment:64 Changed 9 years ago by gleaken

As of 10:44PM EDT, the issue seems to have stopped on the client. Accounts log in and buddy list is populated. Will monitor.

comment:65 Changed 9 years ago by SilverSeraphim

Confirmed. I just logged on and everything seems to be working correctly.

comment:66 Changed 9 years ago by spledger

I can confirm that I had none of my AIM (3 accounts of it) contacts appear in my buddy list, but all of my buddies from other accounts did appear.

I think (and this is mostly based on the number of email alerts and their timing) that we can all assume that while the cause of these errors was not in fact due to Pidgin (rather, it seems like AOL had some issues), it has revealed a flaw in the software that should be fixed as soon as we can figure out where its coming from exactly. I am not a fan of closing 300+ windows, let alone from the same application. Now, I think we ought to decide how exactly this should be handled. I think a better error message at the very least is in order, but also a way to limit the message so that you only get one of them. I'll do some snooping through the Pidgin source code to see what I can find.

comment:67 in reply to: ↑ 44 Changed 9 years ago by kalir

Replying to MarkDoliner:

Another question for people who saw this dialog opening many times: Did you have a buddy icon set? (either specifically for that account, or globally for all your accounts)

When the issue occurred there was no buddy icon was set on my account. The dialog opened approximately 24 times, and then every 4-8 seconds thereafter an additional 1 time, indefinitely. I have 2-4 people on that particular account. Just to be clear, since I am generating activity on this ticket and others are still following, I am not presently experiencing any issues with pidgin or the AIM service.

comment:68 Changed 9 years ago by hackel

I had this problem last night, and logging only my aim account off and on again fixed it without restarting Pidgin. However, all of my aim contacts were removed from their buddy groups and I had to manually add them all back in. Haven't had any problems since then.

comment:69 follow-up: Changed 7 years ago by pra

5 years ago?!

Well, started happening today for me. Windows 7 x64, Pidgin version 2.10.6. Seems to happen every time pidgin connects to icq. Two dialogs appear at once.

comment:70 Changed 7 years ago by MarkDoliner

pra: I'd be interested in hearing if the error stops happening sometime in the next few days. I'm wondering if an ICQ server is not allowing you to see your buddy icon, and if the ICQ folks will fix it sometime soon.

comment:71 in reply to: ↑ 69 Changed 7 years ago by szr

Replying to pra:

5 years ago?!

Well, started happening today for me. Windows 7 x64, Pidgin version 2.10.6. Seems to happen every time pidgin connects to icq. Two dialogs appear at once.

I started getting this today too, also on 2.10.6 (on Windows.) Seems to a new or similar issue cropping up again from ICQ's (AOL's) servers, which gives errors like in the original message.

(14:37:19) oscar: ssi: status is 0x0003 for a 0x0008 action with name no item
(14:37:19) oscar: ssi: Action 0x0008 was unsuccessful with error 0x0003
(14:37:19) oscar: Adding item  gid=0x0000, bid=0x000f, list_type=0x0014 [Buddy Icon], name=1.
(14:37:19) oscar: snac threw error (reason 0x0008: Not supported by host)

comment:72 Changed 7 years ago by nyd

Started happening today for me too. Two popups every time ICQ connects. I don't know if it helps, but it started immediately after Pidgin had trouble connecting to ICQ. The error message was something about being unable to connect to api.login.icq.net. Pidgin version 2.10.6, Windows 7 64bit.

The fixes in this ticket probably worked when the error happened for a different reason, because they don't work anymore.

comment:73 Changed 7 years ago by manners

Another vote for Windows 7 x64 / Pidgin 2.10.6 / Australia (in case there is geography element to the ICQ servers) for this. Started happening in last few hours.

comment:74 Changed 7 years ago by diathesis

This is new to me today. OS X 10.8.1 (Mountain Lion) / Adium 1.5.3, presumably related to the same new problems others are having.

comment:75 Changed 7 years ago by get8p

I am slightly mad. 'Fuck is this? Everything was awesomeface and now I have to lurk for this bug around the web, deleting and upadting the prog, and this piece of shit is still appearing when I start the it. Don't dissappouint me pidgin, you're not some shitty ICQ.

comment:76 Changed 7 years ago by Faldrian

The same issue appeared for me yesterday evening. I still get this message when ICQ logs in. I hope this will be resolved soon.

comment:77 Changed 7 years ago by pra

Happens on linux as well, Xubuntu 12.04 x64, Pidgin 2.10.6. Also, if geography is relevant, I'm in Germany.

comment:78 Changed 7 years ago by Captain Rage

Same here. It started to appear just some day ago, without me upgrading Pidgin or doing anything unusual. Running Pidgin 2.10.6 on a Windows 7 64 bit system.

comment:79 Changed 7 years ago by dude8888

I am also reporting this Issue, started yesterday, out of nothing. changed nothing on system nor did any updates. Windows 7 , 64bit, Pidgin 2.10.6

comment:80 Changed 7 years ago by dustin

Had the same problem yesterday, but it seems to work again now.

I think it's just a temporary server problem, not the bug originally mentioned here, so I posted to ticket #15296.

comment:81 Changed 4 years ago by vpkopylov

I got this error every time I signed in to ICQ (Pidgin 2.10.11). The error code was 0x0003 in my case. It disappeared after setting my avatar in Miranda!

comment:82 Changed 4 years ago by PocketSam

SOLUTION! (probably)

As for the problem was with a newly created account. Error appeared every few minutes. But it had gone after I've uploaded avatar at icq.com site.

comment:83 Changed 3 years ago by MikeGTS

Same issue for Pidgin 2.11.0 (libpurple 2.11.0).

The SOLUTION is as the last two posters mentioned. For ICQ - install the ICQ software on your PC and add a working AVATAR. Doing this on the WEB doesn't seem to work - I get a "time out" error when I'm trying to add an Avatar even though the image is as per their requirements.

Take care.

Version 0, edited 3 years ago by MikeGTS (next)
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!