Re: [SyncEvolution] syncevolution 1.0beta2, n900, and duplicates
[Replying instead of Congwu because it is outside of his working hours.]
On Fr, 2010-03-12 at 16:30 +0000, Stefano Zacchiroli wrote:
So, I can easily reproduce the duplicate problem now, here are my
steps:
- empty the calendar on the N900
- due a slow sync
effect: everything is copied to the N900, fine
- due a standard sync (note: without changing any event on either side)
effect: about 100 events out of 1500 total events get duplicated on
the evolution side on my Linux box.
That looks like the device is sending the Linux side items as "new" and
requests them to be added. Look at the command-line ouput for
"--print-sessions n900" (assuming that n900 is your config name), locate
the session for the standard sync. The statistics shown for
--print-session are always zero, a known limitation of the SyncML engine
when running as server. Therefore it is necessecary to check the logs.
So open the syncevolution-log.html inside that directory. Search for
"Add" or something like it. If unsure, send the log to
syncevolution(a)lists.intel.com.
This is only to verify what the root cause is. If the device sends us
incorrect items, we cannot work around that. It would have to be fixed
on the device.
There doesn't seem to be a pattern, sometime they are
duplicated in
the very same calendar, other times to different calendars
This confuses me a bit. When you say different calendars, do you mean
different calendars in Evolution? How many do you have and how did you
configure the Evolution side? It should always only read/write from one
calendar in normal operation.
--
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.