Comment # 10 on bug 56263 from Patrick Ohly

(In reply to comment #2)
> (In reply to comment #1)

> > > $ syncevolution --daemon=no --status target-config@radicale cards1

> > Oh, I see: the very first time a source is used it goes through yet another
> > code path. The downside of trying to minimize requests - many special cases
> > :-(
> 
> So shall this bug be about tracking that crasher, then?

Yep.

I've fixed the abort. While doing it, I realized that "--status
target-config@..." cannot really report on the status of the target side of the
sync, because nothing in the command line identifies *which* sync is meant to
be reported on: the same target config can be used in multiple sync configs,
therefore the meta data which tracks changes is attached to the sync config,
not the target config.

I know, not obvious, despite being internally consistent :-/

I've opened a feature request for adding more error messages when a target
config is used in operations where it makes no sense: bug #57145.

This also includes an error for attempting to sync the target config (as in
comment #0).