http://bugs.meego.com/show_bug.cgi?id=4026

--- Comment #2 from pohly <[email protected]> 2010-08-10 10:37:18 PDT ---
(In reply to comment #1)
> (In reply to comment #0)
> > BUILD IMAGE: syncevolution-evolution 1:1.0.1-2 (from repo)
> > HARDWARE MODEL: samsung nc 10 (x86); ubuntu 10.04;
> [...]
> > [ERROR] calendar: reading all items: Message did not receive a reply 
> > (timeout
> > by message bus)
> 
> That's the root cause. Access to Evolution Database Server via libecal fails.
> This looks like a timing issue, perhaps related to the fact that this hardware
> is less powerful than your desktop. Sorry, there's nothing that SyncEvolution
> can do about this, this needs to be fixed inside libecal.
> 
> Ross, do you have an idea what might be causing this and how to fix it?  

>From private discussion I gathered that the asynchronous API currently provided
libecal and used in SyncEvolution has design issues which prevent fixing the
problem.

A new asynchronous API is planned, but not available yet.

I might resurrect the Maemo hack of increasing the default D-Bus timeout, but I
am not sure whether that is still possible or would help.

-- 
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
Syncevolution-issues mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution-issues

Reply via email to