Version: (using KDE 4.2.2) Installed from: Debian testing/unstable Packages From: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426293 Reported by: Benjamin Eikel <debian@eikel.org> Dear kopete maintainers, I renamed a group, which contained some ICQ-only, some Jabber-only and some ICQ-and-Jabber contacts. After a few days I wondered why only the Jabber users were online and all ICQ users always offline (only the Jabber part of the combined users was shown online too). I talked to a few of the ICQ users and they told me that they were online. It was not possible to request their authorization again so I logged in with ICQ2Go. There I saw that the whole group was missing in my ICQ contact list. Somehow kopete deleted these users (I am sure that this was done by kopete because I am not using any other IM client [except ICQ2Go for testing this time]) and did not create the new group on the icq server. I got them back by deleting these users from my kopete contact list, adding them again and asking for the authorization. Maybe it is possible for you to reproduce the bug. If I should try to reproduce it please tell me how to log the things kopete does (maybe strace?). Then I will try with a test group or something. Regards, Benjamin Eikel
Hello, I tested it again with the the KDE4 version of Kopete. I took a group (group name contains spaces) and renamed it. After restarting Kopete I have two groups: The old one and the new one. The old one contains all meta-contacts that contain at least one Jabber contact. The ICQ only contacts were moved to the new group. So there still seems to be a bug with this. After that I renamed both groups to the same name (only containing letters). These two groups were not joined so that I have two groups with the same name in the contact list. At last I created a new group and moved the contacts from the two groups with drag and drop to the new one. This time it worked and the contacts are in one group again. Kind regards, Benjamin
Marking as duplicate of bug 146419 Thanks *** This bug has been marked as a duplicate of bug 146419 ***