Version: 0.70.2 (using KDE 4.2.2) OS: Linux Installed from: Debian testing/unstable Packages Some of my work colleagues are also friends and so also on my person IM, as well as the internal work IM system (Jabber). I do not want them to be combined into one contact. I need to be sure that work related stuff goes through the work IM and not my personal one (and vice versa). I keep trying to separate the contacts with change meta contact -> create new meta contact. They then drop out of whatever group they were combined in and go to the top of the tree. Then when I try and drag the two contacts back in to the two groups they should be in, they recombine again. They also seem to recombine after a period of time. For me it is not equal which IM i am talking to someone over, please allow me to keep them separate. If I uncheck "group metacontact" I loose all my groups and just have online and offline.
We don't combine contacts into metacontacts by default, and there's no option for that. So unless your package provider adds in patches that we don't know about, there's no bug here.
Hi, Your own documentation disagrees with you: http://docs.kde.org/development/en/kdenetwork/kopete/using-kopete.html#organise-contacts Second paragraph: "To support this, Kopete introduced “Metacontacts”, which represent the person you want to chat with. One Metacontact contains all the different IM IDs they may have, making it easy to see with a glance at the Metacontact 'smiley icon' whether someone is available, regardless of which IM system they are using right now." This feature conflicts with having an internal Office IM and and external one, where one or more of your colleagues are also friends on an external IM. I was unable to convince kopete to keep such contacts separate. As to distribution, I was using Debian Testing/Unstable. (I provide this comment as FYI, I'm not currently using kopete as I have been assigned to another OS, but when I go back it would be nice to not have this problem) Regards, Thorben
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!