Version: (using KDE Devel) Installed from: Compiled sources I get the error "Your ICQ information request failed. Service unavailable." every time I manage to log on with one of my ICQ accounts. It is account-specific, but I have no idea what it means, only that it is very annoying. For a while, I thought it meant I wasn't really online, until I added myself to my list to make sure.
let me guess, this is happening since this morning/yesterday evening? :) Looks like the old icq server is having problems, it's probably caused by requesting offline messages. Maybe one can ignore not being able to request offline messages.
Interestingly, whatever's broken kopete's ICQ support hasn't damaged licq's version of the ICQ protocol for me, so perhaps an ethereal dump and a bit of picking might show up what's missing between the two.
*** Bug 84741 has been marked as a duplicate of this bug. ***
CVS HEAD does not disconnect on that error, only the version in KDE 3.2 does. Kopete 0.9.x in general is less way strict about icq protocol errors, i.e. it just disconnects if it's really sure that the current connection is useless and cannot be recovered (like password is wrong or you connected too often in the last few minutes).
I compared sim icq packet output with kopete and couldn't really find a difference (except for the snac IDs but that shouldn't make a huge difference). The error for sure is triggered by requesting offline messages. sim-icq still can fetch them, kopete currently cannot. As it suddenly started about one day ago either the AOL morons changed the protocol slightly or the old icq-server is having trouble (I have seen a few database problems some time ago, server wouldn't reply to any of the special ICQ requests). asking on the icq-devel list might be a good idea, maybe somebody else experienced the same problem.
*** Bug 84729 has been marked as a duplicate of this bug. ***
stefan, your assumption is correct. I'd rather not have it ignored, just clarified, i.e. "Error retrieving offline messages could not be retrieved for ICQ UIN 367620603046".
Well, I can login with gaim! But there are no offline Message for me - when I disconnect gaim and try to reconnect with Kopete, it still doesn't work. But you all talk about an old icq server - is there a possibility to connect to a new/other server that works?
How do I get kopete 0.9 ? Will it compile and run with kde 3.2.3 ? Thanks!
See kopete.kde.org, "CVS Access"
Tried. Didn't compile with KDE 3.2.3 (actually, KDE_3_2_BRANCH) Anyway, I've convinced my GF to use Jabber; I got tired of Yahoo, MSN, ICQ, etc. all changing their protocols every now and then. Many thanks, Norberto
> Well, I can login with gaim! But there are no offline Message for me Probably gaim only ignores that error. Unfortunately that is unacceptable because sim-icq still can fetch offline messages so there must be a way to fix this. > when I disconnect gaim and try to reconnect with Kopete, it still doesn't > work. Of course not, the icq server does not stop misbehaving just because you connected with gaim. > But you all talk about an old icq server - is there a possibility to connect > to a new/other server that works? No. There mainly two things: - the oscar protocol invented by aol and used in aim - and an old unused protocol invented by aol and formely used by icq Now the aol morons decided to take the missing icq features (and packets) and wrap them in oscar packets. Now if you send such a wrapped packet it will be forwarded to an old icq-server and the reply will come back also in a wrapped oscar packet (wrapped because the icq part has different endianess). Unfortunately the old icq-server seems to be a bit buggy sometimes. Currently it's the offline message retrieval where it starts getting picky. Some months ago it denied any kind of userinfo retrieval for about two days.
Do we have nobody who can contact some guys at ICQ or AOL and get further information about this misbehaviour? If it is just temporarly or if it is a new server-side-"feature"?
Are you joking? You know that oscar is a properitary protocol, do you?
*** Bug 84794 has been marked as a duplicate of this bug. ***
Should not be there something like an network log window in kopete? Or is it already there and I just can't find it. BTW: AOL can change there protocol ad libitum. I think more people should use jabber instead. But its hard to convince the newbies to install a another programm as far as icq works fine. Maybe it would not so bad if aol would change there protocol and make it incompatible with a large amount of clients.
Run kdebugdialog to enable the protocol debug for protocols. To see it you'll either need to direct it to a file or run Kopete from the console.
btw, for debug output to work in general the kde libraries have to be compiled WITHOUT --disable-debug as it not only disables debugging information inside the libraries itself but also disables the whole kde debug mechanism (i.e. kdDebug() calls do nothing).
and btw, posting debug logs here is unnecessary as the offending packet is already known. The question now is how to fix requesting offline messages.
*** Bug 84837 has been marked as a duplicate of this bug. ***
Very similar, probably identical, problem in Kopete 0.8.3, under KDE 3.2.3 in SuSE 9.0. Using RPMs from ftp.suse.com with all the latest updates. Trying to log on to ICQ fails every time, a connection is established momentarily, then immediately cut off. When trying to log on again, a dialog pops up saying the password was wrong (which it wasn't). Manually entering the password doesn't help - the ICQ icon again begins to flash, contacts pop up as online for less than a second, then the connection is lost again. No error message. There is nothing wrong with the ICQ login and password - both work fine with LICQ. They were working perfectly with Kopete too, until recently. This is what I get on Kopete start-up: duni at dn36ad04:~> kopete duni at dn36ad04:~> libkopete: WARNING: [KopetePlugin* KopetePluginManager::loadPluginInternal(const QString&)] Unable to find a plugin named 'kopete_wp'! Then, on trying to connect to ICQ: MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0 When trying to shut down Kopete: libkopete: WARNING: [void KopetePluginManager::slotShutdownTimeout()] Some plugins didn't shutdown in time! libkopete: Remaining plugins: SMSProtocol libkopete: Forcing Kopete shutdown now. libkopete: WARNING: [virtual KopetePluginManager::~KopetePluginManager()] Deleting stale plugin 'unnamed' The program doesn't seem to shut down correctly, since the prompt in the Konsole doesn't reappear. No idea what's going on.
There is a fix for 3.2 in our CVS now, so you won't be disconnected any more - although you won't get offline messages. We expect to make an 0.8.4 release with this fix and the earlier Yahoo fix in the near future.
*** Bug 84897 has been marked as a duplicate of this bug. ***
First part: The problem with fetching offline messages is a serverside one. My account recently stopped exhibiting this behaviour, I guess aol is fixing their servers now. Second part: All protocol errors now mention the UIN/screenname this error refers to so it's easy to find out what went wrong. For after KDE 3.3 event handling has been planned which will also allow for more detailed error messages.