Version: unspecified (using KDE 4.5.0) OS: Linux When I edit an addressbook contact or a calendar entry within kontact (using an akonadi kolab/imap resource), after a few minutes the old entry reappears. So after the edit I have a double entry, the old and the new version. I have checked directly on the imap server, after the edit both versions of the entry are present there. So I guess what happens is that the kolab resource creates a new entry but doesn't delete the old one, and after the next imap synchronization both entries are visible in kontact. Reproducible: Always Steps to Reproduce: Set up akonadi imap and kolab resource, set imap check interval to 1 minute. Create addressbook entry, then edit this entry. Wait a minute for the imap resource to synchronize. Actual Results: Old entry reappears, both old and new version are visible. Expected Results: Only new version should be there. When trying to reproduce: note that for me the old entry reappears at the end of the address book list, not in alphabetical order. On a side note: When I delete the duplicate entry, often (but not always) plasma crashes. I could not reproduce this crash by just deleting a newly created item.
I have to add that in some rare events this bug is not triggered and the edit is handled correctly.
I had this problem, too. But in my acse it seems to occur if I edit an element that wasn't synced yet. For example if I make a new event and edit the event just a few seconds after that. In this case an error is shown and I have to choose which one of the two versions is the correct one. The error shows that the event was edited on the server on the same time by someone else what can't be! Kontakt 4.6 Beta 4 on KDE 4.6 RC2
I have the same issue here. I have to use the webmail system to delete the duplicate from the imap server manually. I'm using: Platform Version 4.7.4 (4.7.4) Kontact Version 4.7.4
I can't reproduce this with current master (~4.9), any instructions on how to reproduce this?
I don't use the Kolab resource anymore, possibly this has been fixed in newer versions of KDE. Could someone who was also affected check? As far as I am concerned this bug can be closed.
Please close this bug. A newer version has fixed the issue. Everything is now working.