Thanks, Patrick, for your help.
As a first step, run the "--sync refresh-from-server" with
to get the actual data dumped into the N9's syncevolution-log.html file.
Look for a problematic event. Is it in the file?
I have three calendards totaling many hundreds of events (for 2012
only), so I'm shying away from this for now... But I did something
simpler: I changed the description of an event with summary "Test" on
the laptop, and synced (two-way) with loglevel=4. The result is in
The log contains the following lines:
[2012-07-13 12:15:17.788] cannot update record in database (sta=207)
[2012-07-13 12:15:17.789] Database Error --> SyncML status 207
[2012-07-13 12:15:17.789] - Operation replace failed with SyncML status=207
Might this be related?
The terminal output did not indicate any errors, but the event does not
show on the N9 (neither before nor after the sync).
The "Generated" text/calendar is what gets passed to the
backend (KCal). My guess is that the import fails, triggers a bug in the
backend and/or storage.
My experience tells me that such is probably the case, caused by a bogus
event somewhere, which I may not be able to get around hunting down the
But why did you only update these libs and not the rest of
SyncEvolution? Are you perhaps on Debian Wheezy, which now has the
more recent libs but not yet SyncEvolution (currently triggers a
compiler bug on MIPS and thus is prevented from entering Wheezy)?
You could rule out this mismatch as the root cause by installing
18.104.22.168 from syncevolution.org
. Deinstall the system's libsynthesis0,
libsmltk0 and syncevolution packages if apt[itude] doesn't do it
I was hoping this version would enter sid one of these days, but maybe I
should not hold my breath and install from source.