Ticket #666 (assigned defect)

Opened 9 months ago

Last modified 9 months ago

SE W800i and syncml-obex-client: "Unable to commit change" syncing entry with photo

Reported by: marcusb Assigned to: dgollub (accepted)
Priority: normal Milestone:
Component: Plugin: syncml Version: 0.35
Severity: normal Keywords:
Cc:

Description

I get this error when syncing the KDE PIM address book with my SonyEricsson? W800i. Some 70 contacts (out of 225) are transferred successfully, then the phone gives an error. The next time it slow-syncs and duplicates all the previously sent entries.

I don't see any big differences between the contacts that were transferred and those that were not. This is with OpenSync? 0.35 from Debian experimental.

Attachments

w800i-syncml.log (24.1 kB) - added by marcusb on 01/18/08 06:55:08.
Output from msynctool
syncml-obex-client.conf (2.0 kB) - added by marcusb on 01/18/08 06:58:51.
syncml-obex-client.conf
capabilities.xml (2.4 kB) - added by marcusb on 01/21/08 08:25:25.
Capabilities file for the phone

Change History

01/18/08 06:55:08 changed by marcusb

  • attachment w800i-syncml.log added.

Output from msynctool

01/18/08 06:58:51 changed by marcusb

  • attachment syncml-obex-client.conf added.

syncml-obex-client.conf

01/18/08 07:22:25 changed by marcusb

The same phone works well with the IrMC plugin.

(follow-ups: ↓ 4 ↓ 6 ) 01/18/08 14:46:49 changed by dgollub

  • status changed from new to assigned.
  • component changed from OpenSync to Plugin: syncml.

Looks like a capability issue. This means OpenSync? tried to commit/send some contacts with some extended fields, which aren't supported by your mobile. (This could be for example IM or other extended stuff which is only supported by KDEPIM and not by your mobile.)

We have already some facilities to "demerge" fields which aren't supported by the target device. But the capabilities current get discovered... In meanwhile you could write a capabilities file by hand and place it in the member directory of your syncml plugin member. ~/opensync/groupX/Y/capabilities.xml

As reference you can use: http://opensync.org/browser/trunk/misc/capabilities/reference.xml Just remove the nodes which are known to be not supported by your mobile and place it into capabilities.xml

01/18/08 14:47:51 changed by dgollub

... But the capabilities currently don't get discovered ...

(in reply to: ↑ 2 ) 01/20/08 15:00:20 changed by marcusb

Replying to dgollub:

Looks like a capability issue. This means OpenSync? tried to commit/send some contacts with some extended fields, which aren't supported by your mobile. (This could be for example IM or other extended stuff which is only supported by KDEPIM and not by your mobile.)

Yes, it could possibly be the IM addresses. But why does it work when I use IrMC?

01/20/08 15:11:42 changed by dgollub

It doesn't work with IrMC either - i guess. IrMC just doesn't complain about this, which is even worse - since you end up with a "silent" data loss. If you would sync your contacts from kdepim to your mobile via IrMC. And later modify an entry on your mobile and sync it back to kdepim - the IM address is gone - on both sides.

So actually the IrMC isn't better just because it doesn't complain. Not quite sure if IrMc? is even able to throw an error on such case, like SyncML is doing.

You can avoid this kind of dataloss also with such capabilties.xml file.

01/21/08 08:25:25 changed by marcusb

  • attachment capabilities.xml added.

Capabilities file for the phone

(in reply to: ↑ 2 ) 01/21/08 08:27:12 changed by marcusb

Replying to dgollub:

In meanwhile you could write a capabilities file by hand

Tried the attached file, but it still fails in the same way. I'll try to remove some more fields later.

01/22/08 11:26:11 changed by marcusb

It succeeds with only the Name, Email and Telephone fields. I haven't identified the field that caused the problem yet.

01/22/08 21:56:33 changed by marcusb

  • summary changed from SE W800i and syncml-obex-client: Unable to commit change. Error 500 to SE W800i and syncml-obex-client: "Unable to commit change" syncing entry with photo.

Found the offender: the Photo capability.

Any idea why that should be unsupported? It seemed to work with IrMC.