On Tue, 2013-11-26 at 20:19 +0530, Sachin Gupta wrote:
> Hi,
>
> When running syncevo from command line via ssh, getting the following errors:
>
> [WARNING] GConf: Client failed to connect to the D-BUS daemon:
> [WARNING] Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
[...]
> [ERROR] Error allocating system address book
> [INFO] creating complete data backup after sync (enabled with dumpData
> and needed for printChanges)
[...]
> How to resolve this?
Two approaches: if you don't want to use EDS, the default local storage,
then you can compile with "--disable-ebook --disable-ecal
--disable-dbus-service". In the resulting SyncEvolution, there will be
no D-Bus dependency, but also no default local storage. To set up
storage, use:
# Choose a directory where SyncEvolution will
# store the PIM data, using its internal file backend.
# To store in some other backend, like Evolution,
# you'll have to use different "type" and "evolutionsource"
# values in the commands below.
datapath=$HOME/some-directory
# Choose file storage for each of the default sources.
syncevolution --configure \
type=file:text/vcard:3.0
evolutionsource=file://${datapath}/addressbook \
@default addressbook
syncevolution --configure \
type=file:text/calendar:2.0 \
evolutionsource=file://${datapath}/calendar \
@default calendar
syncevolution --configure \
type=file:text/calendar:2.0 \
evolutionsource=file://${datapath}/todo \
@default todo
syncevolution --configure \
type=file:text/plain:1.0 \
evolutionsource=file://${datapath}/memo \
@default memo
When you set up some peer, it'll use these local directories for storage.
The second approach is to ensure that you have a D-Bus session. The
SyncEvolution source has a dbus-session.sh utility script for that, see
http://cgit.freedesktop.org/SyncEvolution/syncevolution/plain/test/dbus-session.sh
--
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]
https://lists.syncevolution.org/mailman/listinfo/syncevolution
