Check existence of needed plugin
Run the following command:
$ msynctool --listplugins
This will list all the available plugins and one that must be present is the following:
If you don't see the above plugin in the output of msynctool, then download the [http://synce.svn.sf.net/svnroot/synce/trunk/sync-engine/plugins/synce-opensync-plugin-2x.py plugin] and copy this file to /usr/lib/opensync/python-plugins or /usr/lib64/opensync/python-plugins for x86-64. After that, when you rerun msynctool --listplugins you should see the synce-opensync-plugin in the output and you can continue with creating an opensync group.
Create OpenSync group
A group between SynCE and your chosen PIM application must be initiated. In this example, Evolution (evo2-sync) is being used -- replace it with the module name (E.g. kdepim-sync).
$ msynctool --addgroup synce-sync $ msynctool --addmember synce-sync synce-opensync-plugin $ msynctool --addmember synce-sync evo2-sync
Start the sync
First make sure SyncEngine is started:
Note:Ubuntu users don't have to start sync-engine manually anymore, sync-engine will be started for them automatically by dbus.
and then all users should sync with OpenSync:
$ msynctool --sync synce-sync
Events one hour off
If events beeing sychronized are one hour (or more) off in Evolution, this may be a problem with the timezone settings.
Try editing the file "config.xml" in the directory ".synce". Look for "AppendDefaultTimesone" and set the value to "1".
Contacts to synchronizing
If contacts are not beeing sychronized from Evolution -> PPC, check if you have something in the "notes" field in Evolution. This seems to prevent that contact from beeing transfered to the PPC.
High memory usage
If memory usage just explodes, this may be caused be a bad event (recurring events with "strange" rules seem to be more prone to trouble) beeing stuck in the syncing-process. What worked for me was removing the "IDB-Files" under the partnership listed in the .sync directory.