On Mon, 2012-07-09 at 14:09 +0200, Patrick Ohly wrote:
> On Mon, 2012-07-09 at 23:30 +1200, Jane Atkinson wrote:
> > On 09/07/12 23:01, Patrick Ohly wrote:
> > > On Mon, 2012-07-09 at 20:12 +1200, Jane Atkinson wrote:
> > >> So I can use a "default" config here. Does that mean that sync-ui
> > >> can be used for running refresh-from-local and slow-sync if
> > >> needed? Or is that only for Evolution-based configurations?
> > > 
> > > sync-ui should work with any kind of sync config. It does not care
> > > about the source configs, because it doesn't know about backends at
> > > all.
> > > 
> > >>> The following steps might make it easier to get a stack
> > >>> backtrace: $ SYNCEVOLUTION_DEBUG=1 gdb syncevolution gdb> run
> > >>> --daemon=no --print-items ja_6120c@webdav calendar ... gdb>
> > >>> thread apply all bt
> > >>> 
> > >> 
> > >> I'll try running these new commands shortly.
> > > 
> > > Thanks, your output has helped.
> > > 
> > > Could it be that libical is not installed on your system? The
> > > crash indicates that SyncEvolution called a function in libical
> > > without checking first that libical was found.
> > > 
> > 
> > Libical wasn't installed, but installing it doesn't seem to have made
> > any difference. The command
> > syncevolution --print-items ja_6120c calendar
> > still produces no output.
> 
> What does the following command print?
> 
> syncevolution --daemon=no --version

Never mind, it can't work. I accidentally introduced a dependency on
libecal: libical is only found when also libecal is present. Will fix
that.

In the meantime, installing libecal should fix the problem.

-- 
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.


_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to