Description of problem: Since to day I can't connect to the icq network anymore. All attempts are stoped by pidgin with a message box telling that the client version is too old. Pidgin also deactivates the icq account automatically. Version-Release number of selected component (if applicable): pidgin.i386 2.3.1-1.el5 libpurple.i386 2.3.1-1.el5 How reproducible: always Steps to Reproduce: 1. Start pidgin 2. Create an icq account if necessary 3. Try to connect to the icq network Actual results: Pidgin doesn't connect to icq and deactivates the icq account Expected results: The connection should be established successfully Additional info:
Even the latest version of pidgin-2.4.2 has the same issue. It appears that upstream is discussing what can be done about this.
Happens to me as well - so I'm back on the good old day, where text consoles were working - centerim still seems to work pretty well. AOL is playing again some 'update protocol' game...
This patch reportedly works on pidgin-2.4.2. I'm doing test builds. # # old_revision [dba36543cdde6db127857b0edfdc3ad1969bbd39] # # patch "libpurple/protocols/oscar/oscar.h" # from [a40e3332eade975c73e344e17bd06d4b99cae751] # to [7853a27f5f8735092ebefef567aaeeccad2a057c] # ============================================================ --- libpurple/protocols/oscar/oscar.h a40e3332eade975c73e344e17bd06d4b99cae751 +++ libpurple/protocols/oscar/oscar.h 7853a27f5f8735092ebefef567aaeeccad2a057c @@ -301,7 +301,7 @@ struct _ClientInfo #define CLIENTINFO_PURPLE_ICQ { \ "Purple/" VERSION, \ - 0x010a, \ + 0x010b, \ 0x0014, 0x0034, \ 0x0000, 0x0bb8, \ 0x0000043d, \
Created attachment 310710 [details] possibly better patch The patch in comment #3 may not be a great idea, as I think someone just randomly changed a number and it happened to work. I've attached an updated patch that makes us mimic the official ICQ6 client, but as this bumps the version we report as from ICQ5 to ICQ6 I don't know if it results in other incompatibilities.
RPMs which include http://www.pidgin.im/pidgin-2.4.2-icq6.patch as mentioned at http://bugs.gentoo.org/show_bug.cgi?id=230389 to fix this are available at ftp://brebs.me.uk/fedora/9/ - this involves 9 RPMs: pidgin* libpurple* finch*
Thanks Paul, ICQ is working now, ICQ accounts are connecting successfully.
Thanks Paul, I can confirm as well, that just forcing instalation of libpurple made my Fedora Rawhide fc10 Pidgin fully operational again. that was quick ;) Just a note - the latest kopete from KDE4 seemed to be unaffected by this issue.
The guys from pidgin have released a new version today. The last time I tried, http://www.pidgin.im was working again, but the new version can also be found on sourceforge. The Changelog says that the problem with ICQ is gone, see http://developer.pidgin.im/ticket/6220 Please roll out the new version soon!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
version in koji works great. please propose it as an update asap. thanks.
This is going to be fixed in a pending security update. I'm adding the 5.2.z flag.
Sorry if this is spam, but the problem is not only in RHEL 5, but also in Fedora (exact: Fedora 9 i386). Do we need another ticket for Fedora? I hope not. But if we do, could someone of you who has more knowledge about how things work here make an appropriate bug report? (And add a reference here...) Thanks!
Tobias, will be in Fedora-updates shortly. You can speed up things by voting for it on https://admin.fedoraproject.org/updates/F9/pending/pidgin-2.4.3-1.fc9 , there's also a download link for the RPM.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2008-0584.html