View previous topic :: View next topic |
Author |
Message |
corey_s Apprentice
Joined: 29 Jun 2003 Posts: 264
|
Posted: Tue Jul 01, 2008 5:41 pm Post subject: [SOLVED] kopete 3.5.9 "icq client too old" |
|
|
Any Kopete users out there suddenly start seeing this message when trying to connect to ICQ this morning/today:
"The server thinks the ICQ client you are using is too old"
Wondering whether anyone knows if this is going to be a general problem for all the linux/free icq clients for a short time, or if someone can recommend me another client to use until this has been fixed in kopete.
Thanks!
EDIT: Solved, most excellent:
Last edited by corey_s on Tue Jul 01, 2008 6:46 pm; edited 1 time in total |
|
Back to top |
|
|
barnie n00b
Joined: 04 Jul 2003 Posts: 21
|
Posted: Tue Jul 01, 2008 5:55 pm Post subject: |
|
|
I'm getting this too (for Kopete).
Licq says: "Unknown sign on error: 0x1C"
-- barnie |
|
Back to top |
|
|
der bastler Apprentice
Joined: 13 Apr 2003 Posts: 257
|
Posted: Tue Jul 01, 2008 6:07 pm Post subject: |
|
|
Confirmed (Kopete 3.5.9). Seems AOL is pushing ICQ6, so we have to wait for updated versions of our clients.
In the meantime I use the web interface (icq2go)... _________________ Tempus fugit.
@frank@troet.cafe |
|
Back to top |
|
|
corey_s Apprentice
Joined: 29 Jun 2003 Posts: 264
|
Posted: Tue Jul 01, 2008 6:08 pm Post subject: |
|
|
Yep -- looks like ICQ had a protocol bump today; other clients are probably experiencing the same issue.
Here's the bug report for kopete: http://bugs.kde.org/show_bug.cgi?id=165502 |
|
Back to top |
|
|
corey_s Apprentice
Joined: 29 Jun 2003 Posts: 264
|
Posted: Tue Jul 01, 2008 6:09 pm Post subject: |
|
|
der bastler wrote: | In the meantime I use the web interface (icq2go)... |
Good suggestion - thanks! |
|
Back to top |
|
|
caspar Apprentice
Joined: 02 Mar 2003 Posts: 228 Location: 240 000 miles away from moon
|
Posted: Tue Jul 01, 2008 6:09 pm Post subject: |
|
|
Same for me (kopete 3.5.9).
A bug has already been filed at kde.org (http://bugs.kde.org/show_bug.cgi?id=165502).
The solution described there works for me, too. Just add the following to your ~/.kde/share/config/kopeterc :
Code: |
[ICQVersion]
Build=0x17AB
ClientId=0x010A
ClientString=ICQ Client
Country=us
Lang=en
Major=0x0006
Minor=0x0000
Other=0x00007535
Point=0x0000
|
_________________ "Dream as if you'll live forever. Live as if you'll die today."
Last edited by caspar on Tue Jul 01, 2008 6:10 pm; edited 1 time in total |
|
Back to top |
|
|
mrsteven Veteran
Joined: 04 Jul 2003 Posts: 1938
|
Posted: Tue Jul 01, 2008 6:10 pm Post subject: |
|
|
Same here... *argh* Why can't more people use Jabber?
EDIT: @caspar: Thanks a lot! Now it works fine again! That's why I love these forums - as soon as you have a problem there's always someone who already has a solution! _________________ Unix philosophy: "Do one thing and do it well."
systemd: "Do everything and do it wrong."
Last edited by mrsteven on Tue Jul 01, 2008 6:17 pm; edited 1 time in total |
|
Back to top |
|
|
der bastler Apprentice
Joined: 13 Apr 2003 Posts: 257
|
Posted: Tue Jul 01, 2008 6:16 pm Post subject: |
|
|
Comment 26: http://bugs.kde.org/show_bug.cgi?id=165502#c26
Just append the following lines to .kde/share/config/kopeterc and restart:
Code: | [ICQVersion]
Build=0x17AB
ClientId=0x010A
ClientString=ICQ Client
Country=us
Lang=en
Major=0x0006
Minor=0x0000
Other=0x00007535
Point=0x0000 |
Works (at least for me).
--Edit--
Ok, duplicate answer (see caspar's post), nevermind. Solution confirmed. _________________ Tempus fugit.
@frank@troet.cafe |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
|
Back to top |
|
|
Genetic Tux's lil' helper
Joined: 09 Jun 2006 Posts: 111
|
Posted: Tue Jul 01, 2008 7:22 pm Post subject: |
|
|
I have the same problem with pidgin. Do you know a solution? www.pidgin.im seems to be somewhat... busy |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
|
Back to top |
|
|
lim_on n00b
Joined: 24 Nov 2005 Posts: 4
|
|
Back to top |
|
|
b3cks Veteran
Joined: 23 Mar 2004 Posts: 1481 Location: Bremen (GER)
|
Posted: Tue Jul 01, 2008 7:59 pm Post subject: |
|
|
If you still use the current stable version of pidgin in portage, use these files:
http://thinknull.com/~ba/public/pidgin-2.3.1.ebuild
http://thinknull.com/~ba/public/pidgin-icq_version_fix.patch
Replace the ebuild file in /usr/portage/net-im/pidgin/ (standard path) with the linked one above, put the patch file in the files folder in the same directory, digest the new ebuild (ebuild /path/to/pidgin-2.3.1.ebuild digest) and re-emerge pidgin (emerge -1 pidgin).
Yes, this is a dirty hack... _________________ I am /root and if you see me laughing you better have a backup. |
|
Back to top |
|
|
Azik Apprentice
Joined: 03 Apr 2005 Posts: 151 Location: Russia, Ufa
|
Posted: Wed Jul 02, 2008 8:48 am Post subject: |
|
|
pidgin-2.4.3 in portage now, sync'n'merge. _________________ From Siberia with Love! |
|
Back to top |
|
|
YuriyRusinov Apprentice
Joined: 21 Jul 2004 Posts: 208 Location: Saint-Petersburg, Russia
|
Posted: Wed Jul 02, 2008 9:22 am Post subject: |
|
|
I'm sorry, but one stupid question, which way I have to apply this patch ? _________________ Best regards,
Yuriy Rusinov. |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
Posted: Wed Jul 02, 2008 9:38 am Post subject: |
|
|
Code: | # cd /usr/portage/
# patch -p1 < /tmp/net-im_licq-1.3.5-logonfix.patch |
|
|
Back to top |
|
|
YuriyRusinov Apprentice
Joined: 21 Jul 2004 Posts: 208 Location: Saint-Petersburg, Russia
|
Posted: Wed Jul 02, 2008 9:59 am Post subject: |
|
|
Thanks a lot. _________________ Best regards,
Yuriy Rusinov. |
|
Back to top |
|
|
Mgiese Veteran
Joined: 23 Mar 2005 Posts: 1609 Location: indiana
|
Posted: Wed Jul 02, 2008 8:56 pm Post subject: |
|
|
lagalopex wrote: | Code: | # cd /usr/portage/
# patch -p1 < /tmp/net-im_licq-1.3.5-logonfix.patch |
|
i did what you suggested :
Code: | # patch -p1 < /home/audiq/downies/licq-1.3.5-logonfix.patch
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|Index: src/icqpacket.cpp
|===================================================================
|--- src/icqpacket.cpp (revision 6387)
|+++ src/icqpacket.cpp (working copy)
--------------------------
File to patch: |
what now ?, i would think i had to go into the licq 1.3.5 dir in portage right ?
thx a lot
ps : just not enough time to play around, already trying to sync portage (just to see if there is a fix available) _________________ I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
Posted: Wed Jul 02, 2008 9:21 pm Post subject: |
|
|
The patch in the licq bugreport will patch the portage-tree and create a patch for the actuall licq, buts thats done in the ebuild |
|
Back to top |
|
|
Mgiese Veteran
Joined: 23 Mar 2005 Posts: 1609 Location: indiana
|
Posted: Wed Jul 02, 2008 9:29 pm Post subject: |
|
|
lagalopex wrote: | The patch in the licq bugreport will patch the portage-tree and create a patch for the actuall licq, buts thats done in the ebuild |
and what have i done wrong ?
thx _________________ I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
Posted: Wed Jul 02, 2008 9:47 pm Post subject: |
|
|
you somehow managed to get the actual licq patch out of it
And that is of course for the licq source... |
|
Back to top |
|
|
Mgiese Veteran
Joined: 23 Mar 2005 Posts: 1609 Location: indiana
|
Posted: Wed Jul 02, 2008 9:50 pm Post subject: |
|
|
lagalopex wrote: | you somehow managed to get the actual licq patch out of it
And that is of course for the licq source... |
lol, that clears up things... so i just wait until portage gets the ebuild-update _________________ I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
Back to top |
|
|
lagalopex Guru
Joined: 16 Oct 2004 Posts: 562
|
Posted: Wed Jul 02, 2008 10:01 pm Post subject: |
|
|
Do that as root:
Code: | cd /usr/portage/ ; wget http://bugs.gentoo.org/attachment.cgi?id=159141 -qO- | patch -p1 ; emerge -av =net-im/licq-1.3.5 |
Really dont know how you messed that up... |
|
Back to top |
|
|
Mgiese Veteran
Joined: 23 Mar 2005 Posts: 1609 Location: indiana
|
Posted: Thu Jul 03, 2008 5:18 pm Post subject: |
|
|
lagalopex wrote: | Do that as root:
Code: | cd /usr/portage/ ; wget http://bugs.gentoo.org/attachment.cgi?id=159141 -qO- | patch -p1 ; emerge -av =net-im/licq-1.3.5 |
Really dont know how you messed that up... |
thx that worked for me _________________ I do not have a Superman complex, for I am God not Superman
Ryzen9 7950x ; Geforce1650 ; kernel 6.5 ; XFCE |
|
Back to top |
|
|
|