osplugin crashed with TypeError in set_uid()

[Osik]

When trying to sync my HTC Touch Diamand and Evolution over synce, I get the following error:

INFO:SynCE:device synchronization complete
INFO:SynCE:initiating prefill
INFO:SynCE:prefill complete
DEBUG:SynCE:requesting remote changes
DEBUG:SynCE:got 3 changesets
DEBUG:SynCE:processing changes for 3 items of item type 0
Traceback (most recent call last):
  File "/usr/lib/opensync/python-plugins/synce-opensync-plugin-2x.py", line 174, in get_changeinfo
    change.uid = array.array('B',guid).tostring()
  File "/usr/lib/pymodules/python2.6/opensync.py", line 192, in set_uid
    def set_uid(self, *args): return _opensync.OSyncChange_set_uid(self, *args)
TypeError: in method 'OSyncChange_set_uid', argument 1 of type 'OSyncChange *'
Member 1 of type synce-opensync-plugin had an error while getting changes: Error during get_changeinfo() method
DEBUG:SynCE:disconnect() called
Member 2 of type evo2-sync just disconnected
Member 1 of type synce-opensync-plugin just disconnected
All clients have disconnected
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
Error while synchronizing: Unable to read from one of the members

In Karmic synce just worked great.

Greeting

Osik

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: libopensync0 0.22-4
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 17 03:02:41 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/opensync/osplugin
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100317.1)
ProcCmdline: /usr/lib/opensync/osplugin /home/username/.opensync-0.22/group1 1
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.utf8
SourcePackage: opensync
Title: osplugin crashed with TypeError in set_uid()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #546305, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

[Osik (stefan-tollkuehn)]

Since I have no right to see the duplicate bug report #546305 I'll post my solution here.

I found at https://qa.mandriva.com/show_bug.cgi?id=54931 a patched opensync.py which seems to be an older version. Lucid Lynx comes with Version 1.3.40 while this patched file is Version 1.3.39.

I replaced the opensync.py file with the attached and could finally sync my contacts, calendars and tasks from my windows mobile phone to evolution.

I'm not very familiar with Python. So I cannot guarantee that this patched file is free from errors. Somebody should look at it.

Best regards

Osik

[Sam Liddicott (sam-liddicott)]

Thanks VERY much for posting that, Osik - If I'd checked here first, I would have avoided losing non-unknown data when I destroyed my sync-groups in an effort to get things working.

[Enrique (elatre)]

It works, thank you!

[Karl Ryder (k-s-ryder)]

I also had the exact same issue on upgrading from karmic to lucid and the older version of the opensync.py file seems to have fixed the problem. Many thanks.

[apienk (andrzej-pienkowski)]

For me, the older opensync.py attached to this thread does not solve the problem. I copied it over /usr/share/pyshared/opensync.py, and re-run sync. The result was a crash (the last lines of output):

Member 1 of type synce-opensync-plugin just sent all changes
All clients sent changes or error
Pipe closed! Exiting.
Pipe closed! Exiting.
Segmentation fault

In Karmic it worked flawlessly. Trying to sync HTC Touch Pro with Lucid amd64.

I couldn't comment on the bug #546305 - no permission to access the page.

[Wladston Viana (wladston)]

Osik,

Amazing! Thanks a lot for sharing this info. It saved me a LOOOOT of time too.

Wonder why they don't fix it for everyone, it's so easy :)

[Jorge Gustavo (jgr)]

Thanks, Osik!

Very valuable information. Thanks for sharing.

Regards

[brody (jens-brodbeck)]

Hello everybody, I would like to add, that I for my person have the VERY same problem as apienk, comment 7! By changing the opensync.py I can "shift" the problem from one error to another. But up to now, I have NO possibility to run syncs successfully. Or is there anybody, who has got a solution for the problem in the meantime?

Best wishes
brody

[Mark Ellis (mark-mpellis)]

apienk and brody, that is a different problem, and therefore a different bug, you should open one up. You also need to provide much more info than the last few lines of msynctool