Re: [SyncEvolution] SyncEvolution and N900 with Evolution - Sporadic addressbook update oddness
Got it! Very subtle.
Isolated but not yet fully understood - I'd love to know more about the
way evolution works that would explain this behavior.
In addition to setting up a VM for testing, I found it convenient to
setup a reverse SSH tunnel from the VM back to my physical machine)
[On the vm: ssh -R2222:localhost:22 username@myphysicaldesktopip]
This allowed me to use X forwarding to place and size the evolution
window somewhere convenient on my physical desktop display
[from physical desktop ssh -Y -p2222 username@localhost]
Once the ssh connection back to the vm was established I would
launch evolution, wait for it to start then ctrl-z and bg to let it run
in the background. (Interesting to note, not waiting for it to start,
would cause a horrible lock of the X server on my physical machine -
another mystery to me...perhaps someone know the answer to that one too)
This does not work, I thought I was just forwarding X and so DBUS
communications for evolution should not be effected...apparently it's
more complex than that though...
Can anyone help with more insight on what's happening?
Meanwhile...I can get back to some real testing.
--Jeff
On Sun, 2010-05-09 at 13:46 +0200, Patrick Ohly wrote:
On Sun, 2010-05-09 at 03:25 +0100, Jeff wrote:
> 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.
I'm not sure whether this bug is still relevant in the N900.
> 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 ?
I'm only using it with 2.28.
> 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.
That is mostly likely the reason, given that restarting Evolution fixes
the problem.
> 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....
There haven't been relevant changes recently, so migrating should be
safe. But note that you may not be able to fall back unless you copy
your .evolution directory first and restore it before falling back.