http://bugzilla.moblin.org/show_bug.cgi?id=9862
--- Comment #11 from pohly <patrick.ohly(a)intel.com> 2010-04-15 00:30:36 PST ---
(In reply to comment #9)
Mostly fixed, except the 'CTR+C'. Usually it hits during the
syncing process,
and SyncEvolution will suspend/abort, but the parent process has no way to know
that the child process was ended because of user interrupt, thus continue
testing..
Perhaps you could read the status.ini of the failed sync to determine whether
it completed or was aborted? There might even be a .ini file parser in Python
which groks our format.
--
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.