From: Martin F. <ma...@si...> - 2006-05-18 02:59:00
|
Hello there, I am the author of al this, so I should know what the problem is. I was not yet able, to reproduce your error (but others though), but this might be due to the old evolution plugin I have. Unfortunately I can't compile the newer one. I am experiencing the same bug as described under http://www.opensync.org/ticket/167 . I will have a look at it this. I saw that I set in gpe_sync.c at about line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what threadsafe is, but I guess the plugin is not. This might be the cause for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;" and give it a go. But I'll have a check for it. So long, Martin On 5/17/06, Andrew Barr <and...@gm...> wrote: > Hi, I'm trying to sync my Sharp SL-5500 running the GPE version of > OpenZaurus 3.5.4.1 and Evolution 2.6.1 on a Debian unstable system. The > gpe-sync plugin is configured to the Zaurus' IP address and my username, > port 22 and use_ssh is 1. evo2-sync is using the default config. SSH'ing > into the Zaurus works fine. I checked the code out of the SVN repo just > about an hour ago. Here is the output of 'msynctool --sync zaurus': > > Synchronizing group "zaurus" > The previous synchronization was unclean. Slow-syncing > Member 1 of type gpe-sync just connected > Member 2 of type evo2-sync just connected > All clients connected or error > Received a entry pas-id-44522C6900000000 with data of size 4 from member > 2. Changetype ADDED > Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4 > from member 2. Changetype ADDED > andrew@192.168.129.201's password: Received a entry > 20060517T004749Z-3935-1000-1-5@r51 with data of size 4 from member 2. > Changetype ADDED > Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4 > from member 2. Changetype ADDED > Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4 > from member 2. Changetype ADDED > Member 2 of type evo2-sync just sent all changes > > Member 1 of type gpe-sync just sent all changes > All clients sent changes or error > All conflicts have been reported > Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit > contact: (null) > Mapping Write Error: Couldn't commit contact: (null) > Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > Member 2 of type evo2-sync committed all changes. > Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1: > Couldn't commit event: (null) > Mapping Write Error: Couldn't commit event: (null) > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1: > Couldn't commit todo: (null) > Mapping Write Error: Couldn't commit todo: (null) > Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1: > Couldn't commit todo: (null) > Mapping Write Error: Couldn't commit todo: (null) > Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1: > Couldn't commit todo: (null) > Mapping Write Error: Couldn't commit todo: (null) > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Member 1 of type gpe-sync committed all changes. > All clients have written > The profile contains the unsupported custom attribute X-LIC-LOCATION. > The profile contains the unsupported custom attribute X-LIC-LOCATION. > The profile contains the unsupported custom attribute X-LIC-LOCATION. > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Member 1 of type gpe-sync just disconnected > The profile contains the unsupported custom attribute X-LIC-LOCATION. > Member 2 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 > > Between the lines "Member 2 of type evo2-sync just sent all changes" and > "Member 1 of type gpe-sync just sent all changes" it stops and waits for > me to type my SSH password for the Zaurus. > > I have tried deleting the PIM database files on the Zaurus and starting > again--the Zaurus is supposed to be empty. There are records in > Evolution that I want copied to the Zaurus on this first sync. > > Any help would be greatly appreciated. > > Regards, > Andrew Barr > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.3 (GNU/Linux) > > iD8DBQBEanpWhuM+Z62a52oRAvNLAJ0eqNhROBkT9vhVCqwGtXXqUhdtuACgoWSZ > fpu9ileKJZzqlMzQaPR/VEU=3D > =3DtiGn > -----END PGP SIGNATURE----- > > > |