Multisync assertion failed (evo2sync)

Bug #279137 reported by Mike Read
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
multisync0.90 (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: multisync0.90

Running Hardy Heron
This is msynctool version "0.19"
using OpenSync version "0.22"

When running msynctool --sync SDA, the output shown at bottom results (contacts and TODOs appear to get synced correctly).
Shown below is the configuration for the group SDA.

Groupname: SDA
Member 1: evo2-sync
 Configuration : <config>
  <address_path>default</address_path>
  <calendar_path>default</calendar_path>
  <tasks_path>default</tasks_path>
</config>

Member 2: synce-plugin
 Configuration : <config>
 <contact></contact>
 <todos></todos>
 <calendar></calendar>
 <file>/My Documents/</file>
</config>

Mapping Write Error: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Error writing entry 370002a0 to member 1: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Mapping Write Error: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Error writing entry 3a000078 to member 1: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Mapping Write Error: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Error writing entry 390003b1 to member 1: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Mapping Write Error: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Error writing entry 30000246 to member 1: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Mapping Write Error: Unable to create event: file e-cal.c: line 4238: assertion `ecal && E_IS_CAL (ecal)' failed
Member 1 of type evo2-sync committed all changes.
Member 2 of type synce-plugin committed all changes.
All clients have written
Member 2 of type synce-plugin just disconnected
Member 1 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects
Pipe closed! Exiting.
Pipe closed! Exiting.
$
$
$ msynctool --version

Revision history for this message
Ron Obvious (dr-ronald-moore) wrote :

I get very similar results - however I'm sync'ing (or rather, trying to sync) between gnoki and evolution (so I suspect the problem is with the evolution plugin and not (only) the synce plugin).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.