[Syncevolution-issues] [Bug 5864] Evolution 2.30: backend shuts down after 10 seconds
http://bugs.meego.com/show_bug.cgi?id=5864
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2010-08-28 11:53:35 PDT ---
(In reply to comment #0)
Primarily it is an issue in our nightly testing (bug #1007). I
suspect that it
does not occur on a desktop only because Evolution keeps the daemons running.
Shut down Evolution, run a sync with a long delay, and the problem might occur.
It does not occur in the syncevolution command line (without daemon) because
the libraries are only opened once. It also does not happen in the daemon
(confirmed by running the experiment), apparently because syncevo-dbus-server
runs a glib main loop.
Need to find a solution - perhaps open a view with a query that never
generates
any data?
Workaround is in "master" branch, but some more work is needed:
commit 614f0390b0f25444434d2519960b0b0bbf6581ee
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Fri Aug 27 18:47:16 2010 +0800
nightly testing: workaround for Evolution 2.30 storage shutdown (BMC #5864)
The D-Bus based Evolution Data Server calendar and contact daemons
(e-calendar-factory and e-contact-factory) shut down after 10 seconds of
inactivity.
Normally libecal/libebook detect that, but not when the client only uses
the
synchronous API ("destroyed" signal not delivered, see e-cal.c). That
affects
SyncEvolution.
This patch ensures that a EvolutionContactSource resp.
EvolutionCalendarSource
remains open throughout the lifetime of the client-test app. This prevents
the storages from shutting down.
This instances are created on demand and deleted when the process quits.
This might be too late for ORBit based Evolution; there were error messages
after all tests succeeded and an assertion failure in ORBit, leading to
a nonzero return code.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.