http://bugzilla.moblin.org/show_bug.cgi?id=8384
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2009-12-02 04:29:25 PST ---
(In reply to comment #0)
This may well be a bug in libecal, but you'll probably know
better...
This very much looks like a but in libecal. There's hardly anything that a
caller can do wrong when calling e_cal_open().
Can you reproduce it? If so, please use "thread apply all bt" to get stack
backtraces. libecal uses multithreading internally. Also check whether
evolution-data-server has crashed. That is a know problem, because all
synchronous ecal/ebook calls hang in that case with Bonobo-based EDS.
I've tried various approaches of dealing with this in SyncEvolution over time,
but it all boiled down to one thing: if EDS or ecal/ebook fail in this way, the
process pretty much has to be restarted.
I'm not sure how to do that with syncevo-dbus-server. A watch dog inside the
main process which does an exec() of itself? Putting each backend into its own
process and use IPC with timeouts?
Note that the "own process" approach might also become necessary at some point
anyway, once we have backends with conflicting libraries. Not the case right
now.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.