Thanks for your quick reply. > Which bug report? As far as I can tell, you are reporting a new bug.
I meant this bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475305 > So what about the bug title? I don't see a "Forbidden (0x43)" anywhere > in the above output. You are definitly right. I can't see either. I've just checked again, and I can some times reproduce this bug. And sometimes I get different behaviors. $ msynctool --sync NOKIA Synchronizing group "Nokia" The previous synchronization was unclean. Slow-syncing Member 1 of type evo2-sync just connected received contact dsession Member 2 of type syncml-obex-client just connected All clients connected or error Member 1 of type evo2-sync just sent all changes Received an reply to our Alert Going to receive 0 changes Received an entry 1 with data of size 4 from member 2 (syncml-obex-client). Changetype ADDED Received an entry 184 with data of size 4 from member 2 (syncml-obex-client). Changetype ADDED Member 2 of type syncml-obex-client just sent all changes All clients sent changes or error All conflicts have been reported (process:13672): libebook-CRITICAL **: file e-book.c: line 349: assertion `book && E_IS_BOOK (book)' failed (process:13672): libebook-CRITICAL **: file e-book.c: line 349: assertion `book && E_IS_BOOK (book)' failed Error writing entry pas-id-49BBDC2200000004 to member 1 (evo2-sync): Unable to add contact Mapping Write Error: Unable to add contact Error writing entry pas-id-49BBDC2200000005 to member 1 (evo2-sync): Unable to add contact Mapping Write Error: Unable to add contact Member 1 of type evo2-sync committed all changes. Member 1 of type evo2-sync just disconnected Received an reply to our sync Member 2 of type syncml-obex-client committed all changes. All clients have written Member 2 of type syncml-obex-client just disconnected All clients have disconnected The sync failed: Unable to write one or more objects Error while synchronizing: Unable to write one or more objects Some time the sync passes successfuly but the it syncs only 2 entries out of ~750 entries. Maybe it is a new bug. > syncml-obex-client command-line tool on its own first before bringing OK. The behavior is really inconsistent. Here are two outputs of two tries with the client you suggested. The first one fails completly with Received an transport error: Forbidden (0x43) The second succeeded very partialy in syncing two phones out of the ~750. The full output (I removed the names and phones for the sake of privacy of my friends...) o...@karo:~$ syncml-obex-client -b 00:12:37:68:EF:C0 11 --slow-sync text/x-vcard contacts --wbxml --identifier "PC Suite" connection with device succeeded Received an transport error: Forbidden (0x43) o...@karo:~$ syncml-obex-client -b 00:12:37:68:EF:C0 11 --slow-sync text/x-vcard contacts --wbxml --identifier "PC Suite" connection with device succeeded Received an Alert for the DS Server at contacts: Type: 206, Last 385, Next 385 Slowsyncing Just received a new session with ID 16 Session 16 reported final. flushing Received an reply to our Alert Going to receive 0 changes Session 16 reported final. flushing Received a added entry 1 of size 84 and type text/x-vcard Data: BEGIN:VCARD VERSION:2.1 N:Name1;Sourname1 TEL;PREF;VOICE:0049xxxxxxxx END:VCARD Received a added entry 184 of size 105 and type text/x-vcard Data: BEGIN:VCARD VERSION:2.1 N:Name2;Sourname2 TEL;PREF;VOICE:xxxxxxxx TEL;WORK;VOICE:XXXXXX END:VCARD Received an reply to our Sync: 200 Session 16 reported final. flushing Session 16 has ended $ I hope this somehow sheds more light on this bug. Thanks again for your effort. Oz. -- ---- Imagine there's no countries It isn't hard to do Nothing to kill or die for And no religion too Imagine all the people Living life in peace ---- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
