[SyncEvolution] Issues with evolution 2.32 and syncevolution 1.1.1a
Patrick Ohly
patrick.ohly at gmx.de
Tue Mar 8 16:06:45 UTC 2011
On Di, 2011-03-08 at 14:25 +0000, David Bremner wrote:
> On Fri, 25 Feb 2011 21:00:30 +0100, Patrick Ohly <patrick.ohly at gmx.de> wrote:
> >
> > No, they need to be rewritten. Matthew confirmed that this happens
> > outside of the backends, so I suspect that it is necessary to run the
> > Evolution UI to trigger the rewriting of gconf keys.
> >
> > I can confirm that running the UI rewrites the keys for me. Tino, does
> > that sound plausible to you? Does it fix your problem?
> >
>
> I seem to be encountering a similar problem: I am using evolution
> 2.32.2-1 from debian sid, and running syncevolution causes
>
> ,----
> | (e-addressbook-factory:24865): e-data-server-WARNING **: e_source_get_uri () called on source with no absolute URI!
> | zsh: segmentation fault /usr/lib/evolution/e-addressbook-factory
> `----
>
> I checked in gconf-editor and all of the keys Matthew mentioned have base_uri="local:"
>
> This is with syncevolution 1.1.99.3 from git. I have previously migrated
> syncevolution to the new format (with 1.1.99.2, I think) , and it seemed
> to be working OK, at least in a few simple tests. Since then, I guess
> several libraries have been upgraded on this machine.
Did you restart syncevo-dbus-server after rewriting the gconf keys? I
doubt that this is the reason (their values shouldn't be cached), but I
want to rule out this explanation.
What does "syncevolution" (with no args) say about the databases and
their URIs?
Finally, just for debugging purposes, what URI is passed to
e-addressbook-factory over D-Bus? Run dbus-monitor and watch out for the
method which opens the address book (not exactly sure what it is).
--
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.
More information about the SyncEvolution
mailing list