Bug 84729

Summary:	icq-module diconnects immediately after connect (since 7 jul 2004)
Product:	[Unmaintained] kopete	Reporter:	Andreas Pietzowski <andreas>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Andreas Pietzowski 2004-07-08 15:01:57 UTC

Version:           0.8.3 (using KDE 3.2.3, SuSE)
Compiler:          gcc version 3.3.3 (SuSE Linux)
OS:                Linux (i686) release 2.6.5-7.75-default

Hi,

I use kopete since over a year now without a problem but since yesterday evening I can't connect to th icq-network. that means, kopete connects to the network and shows me which of my friends are currently online but disconnects immediately from the network. I tried licq and gnomeicu but they both work without a problem with the same ICQ-Account.

I didn't change any software-installation since 3 weeks so it should work as before. Maybe the changed their protocol at 7th of july 2004 but then I'm wondering why licq can connect...

Thanks for information or fixing this bug
Andreas

Comment 1 Markus Wagner 2004-07-08 15:47:00 UTC

Same here. Another ICQ account without any contact entries works fine.

Comment 2 Stefan Gehn 2004-07-08 15:48:19 UTC

Kind of fixed in CVS, there it just displays an errormessage. offline-messaging is not working anymore, the server just returns an error. I hope this is just a temporary problem on the server.

Comment 3 Jan Essert 2004-07-08 18:30:03 UTC

problem persists here with kde 3.2.2. Is there any workaround to fix it with my kopete/kde version (i'd like to chat without compiling kde cvs if this is possible)

Comment 4 Unknown 2004-07-08 19:59:15 UTC

On start with Licq I get a warning in the network-log-window. Just an assumption, but could changed in the icq protocol.?

Log message:
15:36:39: [???] Unknown Various Family Subtype: 0001
     0000: 2A 02 1D D9 00 1A 00 15  00 01 00 00 00 00 00 80   *..Ù............
     0010: 00 05 00 21 00 0A 08 00  10 B1 9B 00 3C 00 02 00   ...!.....±..<...

Comment 5 Stefan Gehn 2004-07-08 20:05:59 UTC

No there is no workaround if the server starts freaking out. One could write a small patch for KDE 3.2 to ignore that specific error of course instead of disconnecting.
In HEAD it was resolved differently nad backporting the changed error handling will be rather hard and might create new bugs in KDE 3.2.
Furthermore there is no new KDE 3.2 release planned so backporting it is a waste of time (that's what you get if apps are inside KDE, you have to live with its release schedule).

Comment 6 Roland Wolters 2004-07-08 21:45:52 UTC

Same here, KDE 3.2.3, FC2, but gaim works!
Maybe someone with knowledge can get in contact with them to write a small patch or something like that?

Comment 7 Gilles Schintgen 2004-07-08 21:49:50 UTC

It would be really great to have such a small patch for KDE 3.2. Please consider the fact that this problem renders kopete useless for many users. Waiting for KDE 3.3 is not exactly the ideal solution.

Comment 8 Norberto Bensa 2004-07-08 22:50:06 UTC

Including Kopete in KDE was a bad idea. Kopete (or any other IM client) NEEDS to be a separate application.

Comment 9 Andreas Pietzowski 2004-07-08 23:08:28 UTC

I don't think it is a bad idea to include an IM into our wonderful desktop. I use SuSE and they offer RPMs for kdenetwork_instant_mesaging.rpm which only includes kopete and some lib stuff perhaps and not the whole KDE! That would be the best way to just update a piece of KDE.

Is it possible to prepare a small rpm for a fixed kopete-version for the current stable KDE?

Comment 10 Stefan Gehn 2004-07-08 23:15:11 UTC


*** This bug has been marked as a duplicate of 84721 ***