Re: [Opensync-users] Some success with Nokia6680 SyncML via Bluetooth

[Daniel G. <dg...@su...>]

On Wednesday 26 July 2006 11:50, Daniel Pittman wrote:
> The specific errors I hit are:
>
> All conflicts have been reported
> Error writing entry libkcal-256941553.509 to member 1: content type was not
> configured Mapping Write Error: content type was not configured
There seems to be a problem of detecting/setting the object type (todo or 
event) of the synced entry from the cellphone. That is the reason why the 
kdepim-sync plugin is not able to write this entry. (The file-sync plugin 
should be able to write this "unknown" object type...) 

So i guess it is a problem of the syncml plugin or maybe of libsyncml.

>
> (Member 1 is the SyncML client connected to the Nokia 6680)
>
>
> Also:
>
> 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.
> QFile::writeBlock: Write operation not permitted
>
> The final error looks like something has failed to write out data as
> expected.
>
>
Can you try to reproduce this and create trace files for more debugging 
information. http://www.opensync.org/wiki/tracing
Also interesting would be the information in which format the vcal or vtodo is 
stored. Use the --dumpinfo paramter of the syncml-obex-client if you use the 
syncml obex connection.

best regards,
Daniel