I'm sorry I can not be more descriptive - I have devoted considerable
time to this potential bug.
If I had managed to find a reproducible set of steps, I would not be
writing here - I would instead be filing a nice detailed Bugzilla bug.
Background:
I wish to use the HTTP server running on my desktop to sync
evolution with an N900. I have been testing in a virtual environment
before trusting the setup with real data on real devices.
The testing:
I am currently testing Contact migration. I expect simple
add/update/remove and conflict handling will work fine so chose to start
with testing the IM fields. There is an existing bug related to
some of the non-standard fields used by Maemo to track bindings between
IM contacts and people contacts For what it's worth, I don't think that
bug is still a bug from what I can tell - I plan to review it and test
it more though.
Environment
(All of this running on a virtual machine to emulate my real
environment)
client: scratchbox N900 with Maemo 5 SDK from March 2010
syncevolution 0.9 (latest available from repository)
server: HTTP server version of sync evolution - latest one from git
peer: desktop Linux Ubuntu 9.04
syncevolution version 1.0beta2 compiled by me
Evolution version 2.26.1
Question:
The wiki (
http://syncevolution.org/wiki/linux-desktop) says
syncevolution SHOULD work with Evolution 2.24 and later....
Has anyone tried it with version 2.26.x ?
The reason I ask is, the symptoms I'm seeing almost seem like they could
be caused by a bug in the evolution ui losing it's link to the evolution
data server.
Symptoms
After a series of operations on contacts on the N900 side
with a sync in between each, to confirm the expected results,
evolution will decide to stop showing updates.
(I leave evolution running and the contact area open - the usual
behavior is that evolution updates the display when the sync
completes)
When this happens, sometimes shutting down evolution and restarting it
will cause the most recent change to be displayed. Other times
shutting down evolution AND running killev followed by restarting
evolution is necessary. In all cases no changes are lost, all edits
and changes seem to be made. In fact if one puts off restarting
evolution and the data server, you can see the changes accumulating
as the debug info is displayed on the console. The gui on the N900
side seems quite happy and thinks the sync went fine but every time
it's run you see the previous run's changes plus the new changes since
the last sync show on the console.
Anyone have any ideas?
My current thought is to try upgrading evolution (and of course it's
data server) to the latest (version 2.6.30)...this might pose other
problems if (as the wiki mentions) the EDS is no longer backward
compatible....