On Wed, 2010-08-04 at 01:58 +0800, Patrick Hendriks wrote: I don't know what "scheduled tasks" is. Care to elaborate? You can invoke the syncevolution as a cron job, but it is a bit involved to set up the right environment and not recommended on a desktop (Evolution gets unhappy when processes outside of the current interactive session access Evolution data). I suggest that you look at the "autoSync" feature instead: $ syncevolution --help --sync-property ? ... autoSync: Controls automatic synchronization. Currently, automatic synchronization is done by running a synchronization at regular intervals. This may drain the battery, in particular when using Bluetooth! Because a peer might be reachable via different transports at some point, this option provides detailed control over which transports may be used for automatic synchronization: 0 - don't do auto sync 1 - do automatic sync, using whatever transport is available http - only via HTTP transport obex-bt - only via Bluetooth transport http,obex-bt - pick one of these Sync intervals can be enabled via additional properties. In the GTK sync-ui there is a checkmark which enables this option with default values. Checking that it really is enabled and works is currently a bit unintuitive. After a reboot and logging it, syncevo-dbus-server should be running and *stay* running. Eventually, after roughly 35 minutes (default autoSyncDelay 5m + autoSyncInterval 30m) it should do a sync in the background. -- 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.