Version: (using KDE 3.5.10) OS: Linux Installed from: SuSE RPMs Starting today I cannot connect to ICQ anymore. The error message is: "The ICQ server thinks the client you are using is too old. Please report this as a bug at http://bugs.kde.org." Since KDE3 still hasn't reached its end of life and since a lot of distributions still ship it in their current release, a quick patch would be great.
I think it'S not a KDE3 problem since I reported the same thing 39 seconds later, but I'm using KDE 4.1.3 https://bugs.kde.org/show_bug.cgi?id=186689
It's the same for me. I use Kopete 0.12.3 in KDE 3.5.5, but I have as well problems with connecting with meebo, where it says that I would be loged in on another platform, so that I think, that it's not just a KDE-problem.
*** Bug 186693 has been marked as a duplicate of this bug. ***
*** Bug 186691 has been marked as a duplicate of this bug. ***
On debianforum.de they say it's a problem with the German ICQ servers but aren't very sure about that. I don't know if their right but here's the link http://www.debianforum.de/forum/viewtopic.php?f=15&t=108609#p686804. It doesn't say much. I'm using KDE 4.2.1 from Kubuntu packages (PPA). Looking forward to the solution.
*** Bug 186403 has been marked as a duplicate of this bug. ***
*** Bug 186689 has been marked as a duplicate of this bug. ***
*** Bug 186700 has been marked as a duplicate of this bug. ***
the following worked for me (kde3, debian): Edit ~/.kde/share/config/kopeterc: [ICQVersion] Build=1042 ClientId=266 ClientString=ICQ Client Country=us Lang=en Major=6 Minor=5 Other=0 Point=0 Good Luck :)
Had the same problem, this workaround works for me in Germany.
The workaround works for me too, in Austria. Thanks!
*** Bug 186706 has been marked as a duplicate of this bug. ***
Working again. Tried similar configurations based on the kopete.kde.org wiki entry for icq which was in Cyrillic (bad thing xD) which didn't work.
(In reply to comment #9) > the following worked for me (kde3, debian): > > Edit ~/.kde/share/config/kopeterc: > [ICQVersion] > Build=1042 > ClientId=266 > ClientString=ICQ Client > Country=us > Lang=en > Major=6 > Minor=5 > Other=0 > Point=0 > > Good Luck :) Works for me too. Thank you.
With OpenSuse 11.1 works this too-thank you!
It worked for me as well, thanks
*** This bug has been confirmed by popular vote. ***
Comment #9 works wonderful. Location : Germany System : SUSE 11.0 Kopete : 50.10 KDE-Version :4.0
*** Bug 186711 has been marked as a duplicate of this bug. ***
This one got lost, I guess. :) http://websvn.kde.org/?view=rev&revision=937550
Strange, I didn't do anything, just logged about 4 hours later, and now that icq plugin works... but About 9pm (CET) I've that problem too....
Czech republic, KDE 3.5.10, Kopete 0.2.17, [comment #9] workaround doesn't work :(
(In reply to comment #22) > Czech republic, KDE 3.5.10, Kopete 0.2.17, [comment #9] workaround doesn't work > :( have you tried the full path " /home/<your_login>/.kde/share/config/kopeterc " ?
(In reply to comment #23) > have you tried the full path " /home/<your_login>/.kde/share/config/kopeterc " > ? sure I was editing my profile :-D, but now He switched the button and it is working in CZE too... I'm not sure where was the catch cause I exited kopete completely, edited kopeterc file and started it again... now I only tried to relogin in already running kopete... I feel a great disturbance in The Force young padawan :-D
*** Bug 186751 has been marked as a duplicate of this bug. ***
> I'm not sure where was the catch cause I exited kopete completely, edited > kopeterc file and started it again... now I only tried to relogin in already > running kopete... > > I feel a great disturbance in The Force young padawan :-D Comment #20 fixed the file containing a valid client id, which is fetched by kopete if the current client id can't connect (I guess). You shouldn't have to workaround manually. It should magically just work :)
(In reply to comment #26) > Comment #20 fixed the file containing a valid client id, which is fetched by > kopete if the current client id can't connect (I guess). You shouldn't have to > workaround manually. It should magically just work :) Yeah :) I saw that kopete tries to fetch it and it was probably that trick.
I think this bug is fixed? - At least it does work for me now, without the manual workaround.
it is fixed.
*** Bug 186876 has been marked as a duplicate of this bug. ***