Bug 218262 - Kopete forgets Meta contacts
Summary: Kopete forgets Meta contacts
Status: RESOLVED DUPLICATE of bug 187311
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 0.80.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-11 12:34 UTC by Paul Ebermann
Modified: 2010-01-03 01:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
some of the empty metacontacts (25.35 KB, image/png)
2009-12-11 12:40 UTC, Paul Ebermann 		Details
metacontacts with names (38.09 KB, image/png)
2009-12-11 12:44 UTC, Paul Ebermann 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Ebermann 2009-12-11 12:34:12 UTC 
Version:           0.80.2 (using KDE 4.3.2)
OS:                Linux
Installed from:    Ubuntu Packages

Regularily (not on each start, but sometimes about weekly) Kopete forgets which contacts are together in one Meta contact.

It also seems to forget the Meta contact names, and the skype contacts are again outside of any group (seems the Skype binding does not support groups).

This is highly annoying.

Also, this seems to add lots of empty meta contacts to my list (those are never online, so are not showed normally), some of which have the names of my contacts, some of which do not have names (or empty names).
Comment 1 Paul Ebermann 2009-12-11 12:40:08 UTC 
Created attachment 38985 [details]
some of the empty metacontacts

Here a screenshot showing some of the no-name empty metacontacts.
Comment 2 Paul Ebermann 2009-12-11 12:44:40 UTC 
Created attachment 38986 [details]
metacontacts with names

Here some of the metacontacts in the list with names, mixed empty ones and ones with contacts. All the same-named were the same metacontact before.
Comment 3 Paul Ebermann 2009-12-11 12:47:15 UTC 
(changed typo in title)
Comment 4 Roman Jarosz 2010-01-03 01:32:13 UTC 

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