Bug 69545

Summary:	icq plugin sometimes does not display comments
Product:	[Applications] kopete	Reporter:	Chris Cheney <ccheney>
Component:	ICQ and AIM Plugins	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal
Priority:	NOR
Version:	0.7.3
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	tcpdump of problem packets

Description Chris Cheney 2003-12-03 07:10:07 UTC

Version:           0.7.3 (using KDE 3.1.4)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.6.0-test11

I was trying to use kopete to communicate with two of my friends. As far as I know both saw my messages but I could only see messages from one of them. I used tcpdump to capture part of their attempted communications and I didn't notice anything suspicious. I have included it here for your entertainment. ;)

Chris Cheney
Debian KDE Maintainer

Comment 1 Chris Cheney 2003-12-03 07:13:09 UTC

Created attachment 3536 [details]
tcpdump of problem packets

The messages from phr0zN were seen fine, however the messages from Bigknock
were not seen at all (none of them!). I have temporarily switched to Gaim 0.72
which shows all messages properly.

Comment 2 Martijn Klingens 2003-12-03 10:18:20 UTC

Subject: Re: [Kopete-devel]  icq plugin sometimes does not display comments

I'm quite sure you're seeing a duplicate of bug 67727 here, with the notable 
difference that Kopete 0.7.x silently discards data with an incorrect 
encoding and 0.8.x shows the error in the chat window. If you compile in 
debug mode, do you see any errors on the console when running Kopete?

Does upgrading to 0.8 beta indeed give the dreaded XML error (or better, fix 
the bug) ?

Comment 3 Matt Rogers 2003-12-31 02:09:56 UTC

Please try upgrading to 0.8 Beta or current CVS and IIRC, your problem should be fixed there. The messages that phr0zN were sending are different from the messages that bigknock were sending. (They're being sent over different channels) 
Thanks for the tcpdump log, very helpful!

Comment 4 Matt Rogers 2004-01-16 02:49:55 UTC


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