Version: 4.3.95 (using Devel) Installed from: Compiled sources I use 2 protocols, Jabber and MSN, and I have 3 individuals with the same name on the same group. Two of these 3 individuals have accounts on both Jabber and MSN. So I have 5 contacts with the exact same name. If I create a metacontact grouping these contacts by "individuals", i have 3 metacontacts: a) MSN, b) MSN+Jabber, c) MSN+Jabber. However, sometimes kopete decides to merge metacontacts b) and c), without any kind of warning or questioning (metacontact "a" is unchanged). I could only stop this behaviour by giving them custom names.
I have a similar problem with automatic metacontact merging. I have contacts with the same names in two different work jabber accounts, and in my personal accounts. I definitely don't want those contacts to be merged into a metacontact, yet they do get merged. Some contacts from the two work jabber accounts get merged, and some contacts from my personal accounts get merged with contacts on the work accounts. Kopete Version 1.0.80 Using KDE Development Platform 4.5.1 (KDE 4.5.1) Could an option be added to NOT automatically merge contacts?
Same here: Auto-Merging of contacts to one meta contact is seriously wrong. There needs to be an option to stop that!
https://bugs.kde.org/show_bug.cgi?id=197003 seems to be the same issue. This issue still occurs with kopete 1.2.0 on KDE 4.8 As this is a regression from previous versions of kopete, could we have an option is disable metacontact grouping?
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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. 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!