http://bugs.meego.com/show_bug.cgi?id=10358
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Depends on| |11044
Summary|Duplicated events appear on |Nokia 2720a: Duplicated
|the phone If I try to add |events appear on the phone
|two or more events in the |If I try to add two or more
|same syncronization. |events in the same
| |syncronization.
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2010-12-13 06:25:10 PST ---
In the second sync, all items are reported as "unchanged" (correct). However,
the engine decides that one item was not sent (successfully) to the phone yet,
and therefore queues it again:
# [2010-11-24 11:26:13.470] Normal sync, item not yet in map -> add to remote
I suspect that there is some relation with a map corruption issue. I'm
currently discussing it with the Synthesis developers and have a potential fix
ready (see bug #11044).
I am not certain how this is triggered. Perhaps an interrupted sync was
involved. The problem is that even wiping out all data and a
"refresh-from-client" or "-server" do not fix the corruption.
Gelexgaray, please do the following:
- archive your .config/syncevolution directory (for later testing)
- remove all .server.ini files inside your phone's config dir
- do a "refresh-from-server" sync
Does the problem still occur?
My expectation is that it goes away, at least temporarily. If it doesn't, then
please wait for the 1.1.0.99.1 release candidate that I am currently preparing
(will announce it on the mailing list), then wipe out the .server.ini once more
and try with that version.
An unsolved problem is how to get .server.ini into a sane state without forcing
users to remove it manually. Perhaps SyncEvolution should detect a "refresh"
sync and remove it before telling the engine about its (possibly broken)
content.
--
Configure bugmail:
http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.