Bug 144621

Summary:	Contacts from "Not in contact list" sometimes reappear after removal (MSN)
Product:	[Unmaintained] kopete	Reporter:	Daan Schulpen <daanschulpen>
Component:	MSN Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED REMIND
Severity:	normal
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Daan Schulpen 2007-04-24 19:04:22 UTC

Version:           0.12.4 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
OS:                Linux

Occasionally a contact will be added to my list under "Not in contact list" without receiving a message from that person. These contacts used to be in my MSN contact list but were removed before I started using Kopete. I'm assuming that they're somehow added because I am still in their contact list.

When removing such a contact they sometimes reappear ~1 second later. But this behaviour is not consistent. Occasionally they will stay removed after the first try, usually after a few tries, and sometimes they refuse to stay removed for days.

I have not been able to consistently reproduce this bug, partially because I'm not 100% sure why those contacts are appearing in the first place. I would, however, be very happy to gather further information if someone can supply test vectors.

Comment 1 Matt Rogers 2007-06-09 07:57:19 UTC

packet captures would be a good thing to have. use ethereal or tcpdump to grab the output. once you have it, it should be possible to arrange to email it to a developer rather than just publicly posting it since it could contain sensitive data such as passwords.

Comment 2 Bram Schoenmakers 2007-08-13 20:56:37 UTC

> I would, however, be very happy to gather further information if someone can supply test vectors.

That would be useful indeed. Are you still able to reproduce?

Comment 3 Matt Rogers 2007-12-11 05:37:41 UTC

If you can still reproduce this and can provide some more data (packet captures and/or debug logs from running Kopete would be the most useful), we'll be happy to take another look. For now though, we'll mark this as resolved until then.