Version: (using KDE 4.3.3) OS: Linux Installed from: Ubuntu Packages # How to Reproduce 1) right click a contact Bob in the Transports group and go to "Groups" => "Move To" => "Friends" 2) Bob is now moved from Transports group to Friends group. Now try move Jane also from Transports group to Friends group. 3) right click contact Jane in the Transports group and go to "Groups" => "Move To" => "Friends" 4) Result is Friends is already pre-selected even though Jane is in fact in the Transports group. Therefore you can not move Jane. # Expected Behaviour 4) There is no pre-selection and you can click on any group therefore moving Jane succesfully to the Friends group.
This bug is still present in KDE SC 4.4.
This bug is probably a duplicate of bug #197073. In my Kopete 1.0.80 (KDE 4.5.2) it seems to be fixed.
Problem still exists with kopete 1.0.80 kde 4.5.2 here. I've now also managed to delete all groups a while back and keep all contacts in the "top level" group due to kopetes bad contacts handling. I can still re-produce this problem although at the moment when I try create a new group(File => Create new group) it seems to work succesfully although I can't find the group, despite show empty groups being ticked or not. Despite the above additional bug, I can still Reproduce this bug as per step 4 in the original report. Hope this helps.
(In reply to comment #3) > Problem still exists with kopete 1.0.80 kde 4.5.2 here. The last used group is already preselected (last used for "move" and another one for "copy") in my case, but there is no problem in that (at least in Kubuntu) - I can still choose the preselected group and it works (contact is moved / copied there). I've thought that it is meant to be so - if you are moving more contacts to the same group, you can find the destination group much faster - it is ticked... (It is probably a little bit confusing, but works great.)
This should be same problem as reported here bug #202862
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!