http://bugzilla.moblin.org/show_bug.cgi?id=8384
--- Comment #2 from jku <jku(a)linux.intel.com> 2009-12-02 05:18:24 PST ---
(In reply to comment #1)
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 think the bonobo explanation may be right: this was on Debian testing and
I've seen that bonobo bug before here. I just tried Tasks and surprise
surprise, it doesn't get anything from eds...
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.
It does seem like a lot of work for this, I've understood that bonobo-eds is
basically end-of-lifed.
I marked this major because I thought this might happen on moblin, and it seems
it doesn't. I don't think this warrants major work, I'm fine with waiting for
Bonobo to go away and expecting EDS to work in future...
--
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.