Re: [SyncEvolution] syncevolution --daemon=yes/no (was: RE: Alarms in the calendar: Evolution vs. vcal)
On Thu, 2010-04-08 at 07:31 +0100, Tino Keitel wrote:
On Thu, Apr 08, 2010 at 08:16:13 +0200, Patrick Ohly wrote:
Yes, I built from source, as I wanted to test the fix for my mobical
issue.
I already use libsynthesis from git.moblin.org at commit
1077b831ecf4dcc7e780bc4d4ec0f7b4326ceb94 (built packages from it),
Ah, so that explains /usr/lib/libsynthesis.so.0 in the stack backtrace.
Neither Yongsheng nor I (on Debian) can reproduce the problem. Hmm, I
just noticed that I don't depend on libxmlparse.so.1 (which you used),
instead I end up using libexpat.so.1.
I suspect that you can avoid the problem using one of these methods:
- configure with --with-xmltok=builtin
- remove libxmltok1-dev and install libexpat1-dev instead
In the meantime I'll try myself whether I can reproduce the problem when
using libxmltok1-dev.
as
syncevolution did not build with the libsynthisis packages from Debian.
My syncevolution version is the mb10458 branch, rebased to master
commit 1e4f3f6b32bba81bc6d71ae08b6382863193fb5b.
FYI, I just merged that branch into master, after Yongsheng made one
more change to it (only apply the alarm workaround to Mobical). Would
you mind retesting that so that we can properly close the bugs as
"verified"?
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.