On Tue, Jul 15, 2014 at 11:18 PM, Patrick Ohly <patrick.ohly@intel.com> wrote:
On Tue, 2014-07-15 at 21:34 +0800, Emfox Zhou wrote:
> On Tue, Jul 15, 2014 at 5:15 PM, Patrick Ohly <patrick.ohly@intel.com>
> wrote:
> Without X, should I use D-Bus or not?


> if yes, how could I made them using it consistantly?

If you disable the GNOME keyring usage, then you don't need D-Bus for
the configure operations.

>         On the other hand, password=111 seems to be found, otherwise
>         the SyncML
>         client would not be allowed to connect.
>         Does "syncevolution --print-config -q c102 addressbook" show
>         the actual
>         databasePassword or "-"?
> It show the actual databasePassword, which is my goolgle password.

So it already wasn't using GNOME keyring.

>         If that fails, you can work around it by disabling GNOME
>         keyring:
>                 syncevolution --configure keyring=no
> it returns "[ERROR] No configuration name specified.", I guess it
> should be
>  "syncevolution --configure keyring=no c102" instead?


Is the "c102 addressbook" source really usable? Let's debug that first.
For that you can run, without D-Bus:

SYNCEVOLUTION_DEBUG=1 syncevolution --daemon=no --print-items loglevel=4 c102 addressbook

It output many lines such as:

   <d:status>HTTP/1.1 200 OK</d:status>

at the end there's some hex code, 16 digits by one line.
What's the complete output of
  syncevolution --daemon=no --print-config -q c102 addressbook

Replace confidentials username/password details as needed...

sync = two-way
uri =
backend = CardDAV
# syncFormat =
# forceSyncFormat = 0
# databaseFormat =
databaseUser = emfoxzhou@gmail.com
databasePassword = jlxxxxxxxxxxxv

Emfox Zhou

GnuPG Public Key: 0xF7142EC2