Ticket #959 (new defect)

Opened 5 years ago

Last modified 5 years ago

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

Reported by: henrik Owned by: bellmich
Priority: normal Milestone:
Component: Plugin: syncml Version: 0.38
Severity: normal Keywords:
Cc: henrik@…

Description

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

Attachments

osync_trace_2.zip (138.7 KB) - added by henrik 5 years ago.

Change History

Changed 5 years ago by henrik

comment:1 Changed 5 years ago by henrik

  • Cc henrik@… added

comment:2 Changed 5 years ago by dgollub

  • Component changed from Engine to Plugin: syncml

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

comment:3 Changed 5 years ago by 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".

comment:4 Changed 5 years ago by dgollub

  • Owner changed from dgollub to bellmich

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?

comment:5 Changed 5 years ago by 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

comment:6 Changed 5 years ago by dgollub

  • Milestone OpenSync 0.39 deleted
Note: See TracTickets for help on using tickets.