i have 2 google calendar resources. After a while( i do a lot of wifi/cable network switching) one of the resources fails to sync. I checked the debugger and i can see there mail address from the second account, which syncs ok. Restart of the resource always helps with this issue. It seems that it fetches the stuff but fails on some unique constraints: {noformat} 27 OK List completed 28 UID MODIFY 286 MIMETYPE (application/x-vnd.akonadi.calendar.todo) PARENT 236 NAME "NAME" REMOTEID "REMOTEID" ENTITYDISPLAY "(\"Default List\" \"view-pim-tasks\" \"\" ())" AccessRights "ACCESS_RIGHTS" 28 OK MODIFY done 29 UID MODIFY 236 MIMETYPE (inode/directory) PARENT 0 NAME "mail@second.resource" REMOTEID "RootCollection" ENTITYDISPLAY "(\"RESOURCE_NAME\" \"im-google\" \"\" ())" AccessRights "C" 29 NO Collection with the same name exists already 30 ROLLBACK 30 OK Rollback completed {noformat} NOTE: start of the log is ommited and names replaced
Are both calendars for the same account? It fails, because a top-level collection called "mail@second.resource" already exists, which most probably means that the other resource owns it.
(In reply to comment #1) > Are both calendars for the same account? It fails, because a top-level > collection called "mail@second.resource" already exists, which most probably > means that the other resource owns it. No every calendar is for separate account. Usually this works ok. But after some time this behavior occurrs.
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!
Sounds like this may have been an Akonadi bug after all, "MODIFY" should not trigger a complain about the name already existing. Feel free to reopen or file a new bug if this still happens with recent Akonadi/KDE PIM.