8:07 a.m.
Hello,
I have set up a remote sync with Funambol. I'd like to take advantage of
the automatic sync. But I've been unable to locate information about
that.
I note that when I start, then close, sync-ui, the syncevo-dbus-server
remains active. So, is it enough that I add
usr/libexec/syncevo-dbus-server
to my startup apps?
TIA - regards, Daniel
BTW, a few remarks about Funambol. As a username, I have put my phone
number _without_ the + (while on the phone, it is there). And I have
kept the default server address http://my.funambol.com/sync, whereas
their web site rather says: http://onemediahub.com:80/sync (which is the
setting on my phone).
--
Daniel CLEMENT
5:16 a.m.
On Sat, 2012-05-05 at 18:07 +0200, Daniel CLEMENT wrote:
Hello,
I have set up a remote sync with Funambol. I'd like to take advantage of
the automatic sync. But I've been unable to locate information about
that.
The configuration options controlling that are documented here:
http://syncevolution.org/documentation/syncevolution-usage
Search for "autoSync".
In the GTK UI there's a checkmark for it which sets autoSync=1.
I note that when I start, then close, sync-ui, the
syncevo-dbus-server
remains active. So, is it enough that I add
usr/libexec/syncevo-dbus-server
to my startup apps?
Yes.
You are bringing up a good point here. On Moblin+MeeGo,
syncevo-dbus-server was started automatically as part of a user session.
Somehow the relevant
file, /etc/xdg/autostart/syncevo-dbus-server.desktop, didn't make it
into the syncevolution.org packages. I'll fix that in 1.3.
Here's what that file should contain:
[Desktop Entry]
Type=Application
Hidden=false
Name=syncevo-dbus-server
Comment=SyncEvolution D-Bus Server
Exec=/usr/libexec/syncevo-dbus-server-startup.sh
The purpose of the shell wrapper script is to delay the starting of the
D-Bus server. That keeps resources free to start up more important
services first.
--
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.
10:03 p.m.
Thanks again Patrick,
Patrick Ohly wrote:
On Sat, 2012-05-05 at 18:07 +0200, Daniel CLEMENT wrote:
> [...]
The configuration options controlling that are documented here:
http://syncevolution.org/documentation/syncevolution-usage
Search for "autoSync".
I should have found this myself, sorry.
In the GTK UI there's a checkmark for it which sets autoSync=1.
> [...]
Somehow the relevant
file, /etc/xdg/autostart/syncevo-dbus-server.desktop, didn't make it
into the syncevolution.org packages. I'll fix that in 1.3.
Here's what that file should contain:
[Desktop Entry]
Type=Application
Hidden=false
Name=syncevo-dbus-server
Comment=SyncEvolution D-Bus Server
Exec=/usr/libexec/syncevo-dbus-server-startup.sh
The purpose of the shell wrapper script is to delay the starting of the
D-Bus server. That keeps resources free to start up more important
services first.
So, even better: I created the missing .desktop file and put it in the
right place (and, of course, syncevo-dbus-server does start). Now I
think my setup is correct, except that I have a small issue with contact
lists. I'll start a new thread for that.
Best regards, Daniel
--
Daniel CLEMENT
11:37 p.m.
Just a remark about the location of the syncevo-dbus-server.
The Debian/XFCE system I'm working on now doesn't have a /usr/libexec.
The syncevo-dbus-server file is under /usr/lib/syncevolution so I
believe the syncevo-dbus-server-startup.sh has to go there too (with the
path properly updated
in /etc/xdg/autostart/syncevo-dbus-server.desktop).
Perhaps some environment variable can take care of this difference.
Best regards, Daniel Clément
Patrick Ohly wrote:
[...] On Moblin+MeeGo,
syncevo-dbus-server was started automatically as part of a user session.
Somehow the relevant
file, /etc/xdg/autostart/syncevo-dbus-server.desktop, didn't make it
into the syncevolution.org packages. I'll fix that in 1.3.
Here's what that file should contain:
[Desktop Entry]
Type=Application
Hidden=false
Name=syncevo-dbus-server
Comment=SyncEvolution D-Bus Server
Exec=/usr/libexec/syncevo-dbus-server-startup.sh
The purpose of the shell wrapper script is to delay the starting of the
D-Bus server. That keeps resources free to start up more important
services first.
--
Daniel CLEMENT
12:42 a.m.
On Tue, 2012-05-15 at 09:37 +0200, Daniel CLEMENT wrote:
Just a remark about the location of the syncevo-dbus-server.
The Debian/XFCE system I'm working on now doesn't have a /usr/libexec.
The syncevo-dbus-server file is under /usr/lib/syncevolution so I
believe the syncevo-dbus-server-startup.sh has to go there too (with the
path properly updated
in /etc/xdg/autostart/syncevo-dbus-server.desktop).
Perhaps some environment variable can take care of this difference.
Autotools should do that automatically. The startup script and .desktop
files use @libexecdir@ and the startup script installs into
$libexec_dir.
--
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.
3738
days inactive
3748
days old
syncevolution@synevolution.org
4 comments
2 participants
participants (2)
-
Daniel CLEMENT -
Patrick Ohly