Bug 112111

Summary: Automatically merge metacontacts with the same name
Product: [Unmaintained] kopete Reporter: Arnt Gulbrandsen <arnt>
Component: libkopeteAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: bigras.bruno
Priority: NOR    
Version: 0.40.0   
Target Milestone: ---   
Platform: unspecified   
OS: FreeBSD   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Arnt Gulbrandsen 2005-09-06 11:22:46 UTC 
Version:           0.9.1 (using KDE 3.3.1, compiled sources)
Compiler:          gcc version 3.4.2 [FreeBSD] 20040728
OS:                FreeBSD (i386) release 5.3-STABLE

Kopete can end up with two instances of the same name in the contact list when jabber is used.

To reproduce you need two machines, one jabber server and something else.

1. Create a contact (e.g using IRC or AIM) on one machine.
2. Create a jabber account on the other machine, and create a Jabber contact with the same name.
3. On the first machine, create the same jabber account.

The first machine will import the contacts for the jabber contacts created in step 2, however, the new contact is not assigned to the existing metacontact of the same name.

Thus you end up with two metacontacts named e.g. "Arnt Gulbrandsen", one which has contacts via IRC, AIM or both, the other with a single contact via Jabber. The two are indistinguishable - you get messages like "Arnt Gulbrandsen is online" for both. It's just that you have to click on the right Arnt.
Comment 1 Olivier Goffart 2005-09-06 12:12:21 UTC 
Currently, Kopete doesn't guess that two contact are the same.
You can merge them manually by drag and dropping the small contacts icon from one meta contact to another.

Kopete should anyway try to guess, when syncing from server, that contact with the same name, or the same id, are the same metacontact, and then merge them.
Comment 2 Stefan Endrullis 2008-04-14 13:50:01 UTC 
I would say this report is a duplicate of bug 78012.
Comment 3 Bruno Bigras 2010-02-14 23:41:39 UTC 

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