syncml-obex-client had an error: An internal I/O error occured

[henrik]

I have earlier reported ​http://opensync.org/ticket/901

As it says in ticket 901, it is not possible to slow-sync ?!

After trying a slow-sync, I try sync'ing again, and get the following: syncml-obex-client had an error: An internal I/O error occured

Full traces attached

[dgollub]

Isn't this about SyncML plugin? Please assign bugs to the related components.

[henrik]

I am trying to assign "my" bugs to the appropriate components.

The problem here is, that I don't really know if it is syncml plugin or engine!

901 looks like Engine, so this one to me looks like Engine too, but I don't really know.

So I assigned it to the more general component, hoping that if "Enginge guys" decided it was not for them, they would reassign to "syncml".

[dgollub]

Looks very SyncML plugin specific. <--- ERROR --- _smlObexEvent: An internal I/O error occured.

JFYI, a very good indicator if it's an engine or plugin error is the error of osynctool:

$plugin had an error: $error-msg

Please always file first a bug against the plugin component in such case (expect your the plugin maintainer and 99% sure it's the engine). The plugin maintainer should decide if it's an engine error not. Engine-folks only have limited knowledge about the plugin-specific implementation itself.

Even if the $error-msg text sounds like an engine issue - it's always the plugin reporting a problem.

Back to the original issue: Could you reproduce the issue with SYNCML_TRACE files? For me this looks like something terminated the OBEX connection. Is this USB, Bluetooth or something else?

[henrik]

I believe the trace files ARE indeed including SYNCML_TRACE.

As per Michaels request, I have used the same dirname for OSYNC_TRACE and SYNCML_TRACE.

/H