Summary: | "ICQ server thinks the client you are using is too old" | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Revasser <revasser> |
Component: | general | Assignee: | Roman Jarosz <kedgedev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | absorbb, admin, alistair_ward, andreas, anmeldungen, apostol, bandobras, basur, Bugs, ccfrodo, christian.nitschkowski, christopherkurc, d.fridrich, dschr, guandalf, holger.maass, mail, mail, mail, nardew, pabel, paolo, qg_tech, rauwen, rjenster, roab, sbriesen, seufert, simontol, tar.anardil, witt-schleuer |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New patch
version info updater commit 568881 |
Description
Revasser
2006-07-11 17:50:11 UTC
I just got it also. I thinbk that AOL changed something on ICQ servers and is demanding a recent protocol implementation (v9 maybe?) I also have this message. I installed V0.12 before some days and since then, i logged in many times until now, as this message cames up. SIM works just fine, but looking at the packet - I don't see it sending any version information, as kopete does *** Bug 130632 has been marked as a duplicate of this bug. *** SVN commit 560990 by rjarosz: fix bug 130630 "ICQ server thinks the client you are using is too old" BUG: 130630 M +2 -2 oscartypes.h --- branches/kopete/0.12/kopete/protocols/oscar/liboscar/oscartypes.h #560989:560990 @@ -237,9 +237,9 @@ const char ICQ_CLIENTSTRING[] = "ICQBasic"; const WORD ICQ_CLIENTID = 0x010A; const WORD ICQ_MAJOR = 0x0014; - const WORD ICQ_MINOR = 0x0022; + const WORD ICQ_MINOR = 0x0034; const WORD ICQ_POINT = 0x0000; - const WORD ICQ_BUILD = 0x0911; + const WORD ICQ_BUILD = 0x0A0F; const char ICQ_OTHER[] = { 0x00, 0x00, 0x04, 0x3d }; const char ICQ_COUNTRY[] = "us"; const char ICQ_LANG[] = "en"; *** Bug 130636 has been marked as a duplicate of this bug. *** Please backport to the 3.5 branch! How long will it go to compile it by myself? I'm running make at my machine since 10 minutes without seeing an end. (Thinkpad R40, i686 1.5GHz, 756MB RAM, KDE 3.5.3, Kernel 2.6.15) George Ruinelli on amd 2000XP it takes half an hour. Bram Schoenmakers will backport it if it doesn't work there because there is diffrent version. Need to compile and test it first Ok, thank you (for your quick answer and also for your quick bugfix!). It now finished (needed only ca. 30minutes). And icq works now again! A debian-package could (in a few minutes) be downloaded from http://ruinelli.ch/archiv#Debian-Pakete A quick edit and recompile and Kopete is logging onto ICQ once again. Thanks for the quick fix! SVN commit 561016 by rjarosz: Backport fix for bug 130630 "ICQ server thinks the client you are using is too old" CCBUG: 130630 M +6 -6 oscartypes.h --- branches/KDE/3.5/kdenetwork/kopete/protocols/oscar/liboscar/oscartypes.h #561015:561016 @@ -232,13 +232,13 @@ /* ICQ Version Characteristics */ const unsigned char ICQ_TCP_VERSION = 0x0008; - const char ICQ_CLIENTSTRING[] = "ICQ Inc. - Product of ICQ (TM).2003a.5.45.1.3777.85"; + const char ICQ_CLIENTSTRING[] = "ICQBasic"; const WORD ICQ_CLIENTID = 0x010A; - const WORD ICQ_MAJOR = 0x0005; - const WORD ICQ_MINOR = 0x002D; - const WORD ICQ_POINT = 0x0001; - const WORD ICQ_BUILD = 0x0EC1; - const char ICQ_OTHER[] = { 0x00, 0x00, 0x00, 0x55 }; + const WORD ICQ_MAJOR = 0x0014; + const WORD ICQ_MINOR = 0x0034; + const WORD ICQ_POINT = 0x0000; + const WORD ICQ_BUILD = 0x0A0F; + const char ICQ_OTHER[] = { 0x00, 0x00, 0x04, 0x3d }; const char ICQ_COUNTRY[] = "us"; const char ICQ_LANG[] = "en"; *** Bug 130639 has been marked as a duplicate of this bug. *** *** Bug 130642 has been marked as a duplicate of this bug. *** *** Bug 130641 has been marked as a duplicate of this bug. *** *** Bug 130645 has been marked as a duplicate of this bug. *** *** Bug 130653 has been marked as a duplicate of this bug. *** *** Bug 130655 has been marked as a duplicate of this bug. *** I'm very sorry but I cannot see here the resolution, how the problem is fixed? What's to do for me so that I can use kopete with ICQ again? *** Bug 130656 has been marked as a duplicate of this bug. *** *** Bug 130659 has been marked as a duplicate of this bug. *** Det you need to compile it from SVN or wait for update from your distribution. for compilation follow this: svn co svn://anonsvn.kde.org/home/kde/branches/kopete/0.12 cd 0.12 make -f Makefile.cvs ./configure cd kopete make su -c "make install" *** Bug 130658 has been marked as a duplicate of this bug. *** There seems to be a fixed .deb at http://bugs.kde.org/show_bug.cgi?id=130656#c4 Florian Schmid made a fixedversion for Debian. Also works with Dapper (checkinstall). http://ruinelli.ch/archiv#Debian-Pakete A big thanks to him. In gentoo fixed version is net-im/kopete-0.12.0-r2 *** Bug 130663 has been marked as a duplicate of this bug. *** Many thanks to Roman. Now it's working fine again. I tried the svn with jingle enabled and it gave me errors. *** Bug 130673 has been marked as a duplicate of this bug. *** *** Bug 130669 has been marked as a duplicate of this bug. *** liam24 you probably don't have some libraries, please look at http://wiki.kde.org/tiki-index.php?page=Kopete+Jabber+Jingle If you still need help come to kopete irc channnel in the freenode IRC Network. Just some ideas: Maybe the protocol version numbers should be specified in the configuration file rather than being hard coded in Kopete. I mean, nowbody knows how often this will happen again. In a first version you could just read those settings from the config file and change them there. This would be a lot more quick and comfortable than compiling the whole program again and again. Later perhaps a mechanism could be implemented to get the latest version numbers from the Kopete homepage whenever the ICQ servers deny access again. Instead of the passive popup that is coming up currently, the user could be asked if he wants to update the version information with the data from the Kopete homepage. *** Bug 130685 has been marked as a duplicate of this bug. *** As workaround, if you don't want to upgrade, you can use Jabber transports (that have been improved in Kopete 0.12) http://wiki.kde.org/tiki-index.php?page=Kopete+Jabber+Transport I have a problem building from cvs. My autoconf is version "autoconf (GNU Autoconf) 2.59" yet the "make -f Makefile.cvs" command tells me "*** AUTOCONF NOT FOUND!. *** KDE requires autoconf 2.53 or newer" Check if you have also automake *** Bug 130688 has been marked as a duplicate of this bug. *** Roman, thanks for the reply. I have all the libraries listed on that site. here is the error I get when I do a Make Collect2: ld returned 1 exit status Error creating ./kopete/protocols/jabber/kopete_jabber.la. Exit status 1. make: *** [all] Error 1 liam24, I never tried compiling kopete with jingle support. Please ask in kopete channel on freenode.net. Found a fixed package for Kubuntu Dapper x86 here: http://www.kde-apps.org/content/show.php?content=41143 I've updated the suse packages in the build service: Repository URLs are: http://repos.opensuse.org/KDE:/KDE3/ http://repos.opensuse.org/KDE:/Backports/ Masochists can navigate in there and install by hand. I'll have a Yast Online update out in the next couple of days. *** Bug 130703 has been marked as a duplicate of this bug. *** *** Bug 130708 has been marked as a duplicate of this bug. *** Supporting Jens Rutschmann, I think it would be a great thing... especially for these oscar/msn/yahoo closed protocols I have some missing libraries Jingle, XMMS... Any locations for a fixed SUSE RPM? *** Bug 130715 has been marked as a duplicate of this bug. *** *** Bug 130719 has been marked as a duplicate of this bug. *** *** Bug 130757 has been marked as a duplicate of this bug. *** The deb of Mr. Runelli is working, but have a Huge problem - it's version in system appears 0.12.0-1 and in Debian Etch (for example) it must be 4:3.5.3-1 *** Bug 131210 has been marked as a duplicate of this bug. *** This bug is actual again :( Created attachment 17185 [details]
New patch
SVN commit 568263 by rjarosz: Fix for The ICQ server thinks your client is too old CCBUG: 130630 M +1 -1 oscartypes.h --- branches/KDE/3.5/kdenetwork/kopete/protocols/oscar/liboscar/oscartypes.h #568262:568263 @@ -237,7 +237,7 @@ const WORD ICQ_MAJOR = 0x0014; const WORD ICQ_MINOR = 0x0034; const WORD ICQ_POINT = 0x0000; - const WORD ICQ_BUILD = 0x0A0F; + const WORD ICQ_BUILD = 0x0BB8; const char ICQ_OTHER[] = { 0x00, 0x00, 0x04, 0x3d }; const char ICQ_COUNTRY[] = "us"; const char ICQ_LANG[] = "en"; This is now the second time that this message appears and I know that actually ICQ is the bad party which tries to fool 3rd party clients. But why can clients like Trillian and GAIM cope with these protocol changes without recompiling? Would be interesting whats the difference with kopete. Thanks for information. Have a nice day Andreas I don't understand, I didn't change anything and today my ICQ is working in the 0.12.0 version. In addition, my KDE is the 3.5.3, maybe this is the key (some library?) *** Bug 131598 has been marked as a duplicate of this bug. *** *** Bug 131599 has been marked as a duplicate of this bug. *** i guess "other" clients increase their internal build number when they get booted with the "client too old" reason, then reconnect, repeat until !fail, then store the build number that worked in the ini file. When it is really an only incrementing integer then you just postet the solution of our kopete-ICQ problem, right? Or does someone have connections to the GAIM developers or is someone involved in the programming of that client to find out their solution? In my opinion a patch every one and then is not the solution. What do you think? re #60: gaim is open source, too.... someone with more understanding than me should just look at it. licq also works with icq right now, with no errors... and my licq version is 6 weeks old. but i think the "centralized database of working client version numbers" is another good idea. just have it store FAILED versions as well, so that everyone who fails to connect reports it to the database as well; narrows down the hunt for working numbers, as well as shows mirabilis that they cant lock out other OSes. Gaim use version of ICQ PRO, but when I was implementing buddy icons they didn't work when we identify Kopete as old pro client. I'm working on fix that will allow change version without recompilation. This is the error I got as well - seems like a lot of us have gotten this bug. It might help to tell you that I just this minute received and installed a Kopete update, installed automatically. Kopete worked fine before this. In message at 31 juli 2006 21:50 Andreas Pietzowski: [bugs.kde.org quoted mail] I do't know. I use now another distributive, kubuntu, and not have problem with kopete. *** Bug 131636 has been marked as a duplicate of this bug. *** Request re-open. Message is back since 1st of August. Yes I agree but not since the swiss national holiday, here it was already one day before. Please tell us how to fix as soon as possible :) You have to recompile it with this http://bugs.kde.org/attachment.cgi?id=17185&action=view patch I installed LICQ instead. After installing the packages from Mr. Ruinelli it still doesn't work. Also, Adept Package manager finds an update for Kopete, but still nothing happens. What to do?? Ana: the package from Mr Ruinelli is for old fix. The icq blocked older versions again 31.7.2006 so you have to recompile kopete with new patch. I'm working on autoupdate stuff hopefully it will be ready today so than these problem will go away. well, if simply changing a version-number inside kopete satisfies those guys at icq -- why not making this changeable from inside kopete or at least a config-file instead of patching and recompiling? I did a package for Ubuntu Dapper, maybe it works also with Debian. Needs speex an KDE 3.5.3, cause of Jingle-Support. http://www.floyd-online.com/Download/kopete_0.12.1.1-1_i386.deb arne anka I'm working on that made a debian/unstable package 3.5.4-1 with the patch mentioned in #69 (mostly for myself) and put it up to http://www.ginguppin.de/kopete_3.5.4-1_i386.deb hopefully you guys will not spoil my download-limit ;-) ps: it's kopete 0.11.3 -- don't know why the debian-name does not reflect that Thanks a lot for the compiling, Florian. That saves me another half an hour! I was just about to open another bug report when I saw this one. Isn't it incredible what can happen when somebody at ICQ Inc. changes a little version number in some server database? loool Sebastian No problem. But i forgot a thing. If you want to use Jabber with my package you need to have ortp 0.7.1 installed. So I made a .deb with it. worked under Dapper. http://www.floyd-online.com/Download/ortp_0.7.1-1_i386.deb *** Bug 131680 has been marked as a duplicate of this bug. *** I messed up something with the versions in the package posted below. So Dapper wants to update the new, fixed Kopete. Uploaded a version with the correct Versionnumber, so that this problem should be solved. http://www.floyd-online.com/Download/kopete_4:3.5.3-0ubuntu0.5-1_i386.deb You also need this: http://www.floyd-online.com/Download/ortp_0.7.1-1_i386.deb and speex installes (should be universal) Hope it helps. rather late, but at least now, there is an updated kdenetwork-rpm for Fedora5/i386 (with its source rpm along). it contains kopete-0.12.1-release with the patched oscartypes.h. you can simply use it with rpm -Uvh, replacing the original fedora package. i hope it helps :-) http://crystal.cnetworks.ath.cx/linux/software/ *** Bug 131700 has been marked as a duplicate of this bug. *** *** Bug 131709 has been marked as a duplicate of this bug. *** *** Bug 131713 has been marked as a duplicate of this bug. *** SVN commit 568881 by rjarosz: add version info updater - version info for icq/aim is stored in kopeterc config - kopete automatically downloads new version from kopete.kde.org if login fails with "client too old" :) CCBUG: 130630 CCBUG: 131598 M +2 -1 Makefile.am M +1 -0 aim/aimaccount.cpp M +1 -0 icq/icqaccount.cpp M +11 -9 liboscar/aimlogintask.cpp M +11 -0 liboscar/client.cpp M +6 -0 liboscar/client.h M +5 -0 liboscar/connection.cpp M +1 -0 liboscar/connection.h M +14 -12 liboscar/icqlogintask.cpp M +13 -18 liboscar/oscartypes.h M +31 -3 oscaraccount.cpp M +2 -0 oscaraccount.h A oscarversionupdater.cpp [License: GPL (v2+)] A oscarversionupdater.h [License: GPL (v2+)] can someone wrap up svn commit 568881 into a .diff file? Created attachment 17205 [details]
version info updater commit 568881
Kopete 0.12.2 will be released soon so if you want to do packages than maybe
wait till it's released.
Just an idea. Kopete can download new identification string directly from kopete.kde.org. For example: when "Your client is too old" error will occur, kopete doqwnloads a file from kopete.kde.org/icqrc or something similar, and try to connect again. Ben, the idea is already implemented :) commit 568881 *** Bug 131778 has been marked as a duplicate of this bug. *** But can anybody tell me why gaim doesn't need such a thing and works withouth problems? I don't know, but are there big differences between the implementation in gaim and kopete? Because IMHO such problems mostly occure with kopete. Dominik, Gaim uses icq2003b identification Hm..is that bad? I think if it works more reliable, it would be the better choice. Or am I wrong? When I was implementing buddy icons for ICQ it didn't work till I used icq5 identification. Anyway with commit 568881 this problems should go away. *** Bug 131813 has been marked as a duplicate of this bug. *** *** Bug 131847 has been marked as a duplicate of this bug. *** *** Bug 133109 has been marked as a duplicate of this bug. *** *** Bug 133877 has been marked as a duplicate of this bug. *** |