On Wed, 2012-03-14 at 21:53 +0100, michael.kummer(a)gmx.net wrote: The end of the command line tool outpuit should have had instructions on what to do in this case. "unexpected slow sync" is not allowed to proceed in the default config (but that can be changed with preventSlowSync = 0). This is your opportunity to refresh from the server, the client, or allow the slow sync. See the "--sync" command line operation for more details. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter.

Hi - michael.kummer(a)gmx.net wrote on Thu, 15 Mar 2012 17:09:29 +0100: I occasionally encounter a possibly related problem (syncevolution client on N9, syncevo-http-server on the laptop). This is how things occasionally go wrong: - I do a nontrivial edit (exceptions to recurring events, ...) to a calendar entry on the laptop. - Subsequent sync fails; slow sync is avoided thanks to configuration. - On the N9, I --sync refresh-from-server, which fails with "could not save calendar" - Due to the failed refresh-from-server, the calendar on the N9 has been emptied, except for one stray entry (the edited one?). - I manually delete the stray entry on the N9. - Subsequent --sync refresh-from-server works, and all goes back to normal. Not sure this vague and unreliable description helps. For me, the key step is the deletion of the stray calendar entry, by deleting the entire calendar on the N9 if necessary (which is impossible if the problem occurs with the default calendar). I have been wanting to ask for help myself, or file a bug report, but I have been unable to reproduce the problem reliably. Justus