Bug 84794

Summary: connection failure to icq, it worked fine until this night!
Product: [Unmaintained] kopete Reporter: umberto mantello <u.mantello>
Component: generalAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version First Reported In: 0.8.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description umberto mantello 2004-07-09 11:20:45 UTC
Version:           0.8.2 (using KDE 3.2.2,  (testing/unstable))
Compiler:          gcc version 3.3.3 (Debian 20040401)
OS:                Linux (i686) release 2.6.6.201

output prompted when i try to connect to icq

>MNG error 1029: Chunk out of sequence; chunk TERM; subcode 0:0
>QGArray::find: Index 0 out of range

The connection to msn still work!!!
I have only two accounts: ICQ and MSN, the first today won't work: until yesterday kopete worked fine in every feature.
It tell me that the password provide is incorrect, but it can't be!
The account with this password will work under ICQ for windows.
Tanks!
i have loaded all the plugins.
Comment 1 Jason DePeaux 2004-07-09 12:00:24 UTC
I've seen this too, upon re-entering my password, it connects for a moment, shows who's online and immediately disconnects. It just started today, I think ICQ might have changed their protocols.
Comment 2 umberto mantello 2004-07-09 12:14:09 UTC
I don't think icq servers have changed their protocol, because now i am using licq and it works! 
Comment 3 Jean Pierre Wenzel 2004-07-09 12:33:50 UTC
Same Problem here. ICQ2go works from time to time, but quits occasionally with a database error (#60).

Seems that ICQ network has some problems.
Comment 4 Stefan Gehn 2004-07-09 12:52:05 UTC

*** This bug has been marked as a duplicate of 84721 ***
Comment 5 Stefan Gehn 2004-07-09 13:16:44 UTC
>I don't think icq servers have changed their protocol, because now i am using
> licq and it works! 
licq just ignores that error, you can see it in its debug output. Kopete in KDE 3.3. won't disconnect either, still offline-messages aren't working right now (so something _must_ have changed on the server)