Re: [SyncEvolution] Problems when auth to google carddav
On Tue, 2014-07-15 at 11:01 +0800, Emfox Zhou wrote:
On Tue, Jul 15, 2014 at 1:59 AM, Patrick Ohly <patrick.ohly(a)intel.com>
wrote:
Now it complains for the missing DBus server or so, either I should
recompile
syncevolution without dbus or ensure the dbus is running,
You need D-Bus when running syncevo-http-server.
syncevo-http-server http://localhost:9000/ --start-dbus-session
&
syncevolution --configure --sync-property syncURL= \
--sync-property peerIsClient=1 \
--sync-property remoteDeviceId="IMEI:xxxxxxxxxxx" \
--sync-property username=emfox \
--sync-property password=111 \
--sync-property SSLVerifyServer=0 \
--source-property uri= \
--source-property sync=none \
c102
syncevolution --configure --source-property backend=carddav \
--source-property
database=https://google.com:443/carddav/v1/principals/emfoxzhou%
40gmail.com/lists/default/ \
--source-property databaseUser=emfoxzhou(a)gmail.com \
--source-property databasePassword=jlxxxxxxxxxxxxxdlv \
c102 addressbook
You are using different D-Bus sessions here: one for syncevo-http-server
and the syncevo-dbus-daemon started by it, one for configuring
SyncEvolution. I can imagine that this causes problems with GNOME
keyring.
Better run all commands in the same shell, where a D-Bus session already
exits. Or are you running these commands on a remote server via ssh?
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 "-"?
Please enhance the debug level and then try again to sync from your
phone:
syncevolution --configure loglevel=4 c102
In the resulting syncevolution-log.html, what does it say about password
lookup?
If that fails, you can work around it by disabling GNOME keyring:
syncevolution --configure keyring=no
syncevolution --configure password=111 c102
syncevolution --configure databasePassword=jlxxxxxxxxxxxxxdlv c102 addressbook
However, I'd prefer to understand first why it fails.
--
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.