[kaddressbook] [Bug 323717] New: Creating a new category for a contact creates a duplicate entry when re-editing contact categories

[Ioannis Ramfos]

https://bugs.kde.org/show_bug.cgi?id=323717

            Bug ID: 323717
           Summary: Creating a new category for a contact creates a
                    duplicate entry when re-editing contact categories
    Classification: Unclassified
           Product: kaddressbook
           Version: 4.11
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: isr81 at freemail.gr
                CC: tokoe at kde.org

When creating a new contact and a new category is created and assigned to this
contact, everything works as expected when the data entry is complete ("OK"
pressed in the "Add tags" window and the "New Contact" window).
However, when editing the contact, upon reentry in the categories list
(pressing the "..." button), the assigned tag is recreated and assigned two
times. If "Cancel" is pressed, the contact is not changed as expected. 
If "OK" is pressed in the "Add tags" window with both identical tags selected,
the tags are duplicated in the contact entry as well (and in the vcf file). 
If "Nepomuk Cleaner" is executed before or after the editing of the contact,
the duplicate entry is removed and is not recreated upon further re-edits of
tags.

The same bug occurs when adding more than one tags.

Reproducible: Always

Steps to Reproduce:
1. Create a new contact
2. Add a new Category (tag) for the contact
3. Confirm the entry by pressing "OK"
4. Re-edit the contact and press the "..." button to update the categories

Actual Results:  
The assigend category is duplicated and both tag instances are selected 
If OK is pressed and the contact is saved, the tags will remain duplicated for
the contact.

Expected Results:  
The assigned category appears only once.

This bug did not occur in 4.10.5 and possibly previous 4.10.x versions.

-- 
You are receiving this mail because:
You are the assignee for the bug.