I see no problem in your configuration, so I guess it's the unstable eds's
fault.
Yves-Alexis wrote:
>> Ok, addressbook sync seems to run pretty fine (I'm using
HEAD from your
>> git branch), but calendar doesn't. I tried to use uri=N900 (which is the
>> calendar name on the device, you can have multiple calendars) but it
>> doesn't work. Do you have any idea on what happens?
> Is that still the same error as before?
>> Did you manage to sync calendars?
> No, I didn't give a try. The phone currently is not on my hand anymore, so I
> even cannot try at this moment.
Ok, I tried to give another shot. I had a problem in my configfile, the
source was configured as:
type = addressbook:text/x-calendar
so there was no way it could work.
Now I have:
type = calendar:text/x-calendar
evolutionsource=Phone
which I guess is fine. When I try:
syncevolution delirium calendar with no evolution process running, I get:
First ERROR encountered: calendar: reading all items: Message did not
receive a reply (timeout by message bus)
If I start evolution and retry the sync, I get the same message, and on
the evolution window I get a popup saying:
The Evolution calendar has quit unexpectedly.
Your calendars will not be available until Evolution is restarted.
and the /usr/lib/evolution/e-calendar-factory is killed. (and in evo
terminal output I have the following message)
(evolution:862): libecal-WARNING **: e-cal.c:398: e-d-s proxy died
Though, I'm using evolution 2.29.5 which might be a bit unstable.
Cheers,
--
Yves-Alexis
Best Regards,
Congwu