TypeError: in method 'OSyncChange_set_uid' again...

[Iain Buchanan]

Hi all,

TypeError: in method 'OSyncChange_set_uid', argument 1 of type 'OSyncChange *'

This has come up a number of times for me, and it's always a bit of
voodoo to get rid of it. As a result I haven't synced my phone for 6
months or so (which is why I've been so quiet here!)

Today I decided to try it again, and after much reinstalling and
patching which didn't fix it, I factory reset my phone (Treo Pro).

I deleted all synce related settings from my PC and re-created the
partnership, and it worked! Synced flawlessly about 6 or 7 times. I
restored the contacts from evolution, started editing them, adding
details etc. (all from evolution) and all syncs were fine.

Then I added 2 calendar entries from the mobile, and when I try and
sync, I get this error again! Attached is the msynctool output and the
sync-engine log file...

I know Dr Gow was looking into this some time ago but the results were
not repeatable for him. There is some talk about it here:
https://www.opensync.org/ticket/1131 but the patch didn't work for me
this time (it's worked previously I think...)

Does anyone have any thoughts on this? I'm happy to try any patches or
start again from scratch, since I've just done a factory reset anyway!

Much appreciated!

[Mark Ellis]

Post by Iain Buchanan
Hi all,
TypeError: in method 'OSyncChange_set_uid', argument 1 of type 'OSyncChange *'
This has come up a number of times for me, and it's always a bit of
voodoo to get rid of it. As a result I haven't synced my phone for 6
months or so (which is why I've been so quiet here!)
Today I decided to try it again, and after much reinstalling and
patching which didn't fix it, I factory reset my phone (Treo Pro).
I deleted all synce related settings from my PC and re-created the
partnership, and it worked! Synced flawlessly about 6 or 7 times. I
restored the contacts from evolution, started editing them, adding
details etc. (all from evolution) and all syncs were fine.
Then I added 2 calendar entries from the mobile, and when I try and
sync, I get this error again! Attached is the msynctool output and the
sync-engine log file...
I know Dr Gow was looking into this some time ago but the results were
https://www.opensync.org/ticket/1131 but the patch didn't work for me
this time (it's worked previously I think...)
Does anyone have any thoughts on this? I'm happy to try any patches or
start again from scratch, since I've just done a factory reset anyway!
Much appreciated!

Hi Iain

Has anyone seen this on other than fedora ? Iain, what are you using ?

My opensync.py has slightly different code than this, on ubuntu. I'm
wondering if this is a swig issue, since the interface file is really
quite simple. What version on swig is on yours ?

Mark

[Iain Buchanan]

Post by Mark Ellis

Post by Iain Buchanan
Hi all,
TypeError: in method 'OSyncChange_set_uid', argument 1 of type 'OSyncChange *'

...

Post by Mark Ellis
Hi Iain
Has anyone seen this on other than fedora ? Iain, what are you using ?

Gentoo. There was another user with the same problem a while back, not
sure what they had.

Post by Mark Ellis
My opensync.py has slightly different code than this, on ubuntu. I'm
wondering if this is a swig issue, since the interface file is really
quite simple. What version on swig is on yours ?

swig-1.3.40, and you?

I tried recompiling swig, libopensync, and msynctool (just in case) but
I still get the same error. Do you think it's worth trying earlier
versions of swig? Should I have to recompile libopensync afterwards?

thanks,

[Mark Ellis]

Post by Iain Buchanan

Post by Mark Ellis

Post by Iain Buchanan
Hi all,
TypeError: in method 'OSyncChange_set_uid', argument 1 of type 'OSyncChange *'

...

Post by Mark Ellis
Hi Iain
Has anyone seen this on other than fedora ? Iain, what are you using ?

Gentoo. There was another user with the same problem a while back, not
sure what they had.

Post by Mark Ellis
My opensync.py has slightly different code than this, on ubuntu. I'm
wondering if this is a swig issue, since the interface file is really
quite simple. What version on swig is on yours ?

swig-1.3.40, and you?
I tried recompiling swig, libopensync, and msynctool (just in case) but
I still get the same error. Do you think it's worth trying earlier
versions of swig? Should I have to recompile libopensync afterwards?

I've got 1.3.36 on ubuntu karmic. Anybody out there know what version
fedora core 11 uses, since that seems to be where most of the problems
are.

You could try an earlier version, no idea if it'll help though, and yes
you'll need to recomp libopensync afterwards. I'll try and do a little
experimenting.

Mark

[Aurelien Bompard]

Post by Mark Ellis

Post by Iain Buchanan
swig-1.3.40, and you?

I've got 1.3.36 on ubuntu karmic. Anybody out there know what version
fedora core 11 uses, since that seems to be where most of the problems
are.

I'm on Fedora 12 and I have 1.3.40 too. Fedora 11 has 1.3.39.


Aurélien

[Iain Buchanan]

OK I've some some playing:

* swig 1.3.36 causes "pipe closed, segmentation fault" in mscyntool
* swig 1.3.38 causes the same TypeError (different line, same function)
* swig 1.3.39 causes the same TypeError
* swig 1.3.40 I didn't try again (original TypeError)

in between each version of swig I recompiled libopensync, msynctool,
libopensync-plugin-evolution2, and libopensync-plugin-python. I also
restarted sync-engine and re-plugged the device.

I went back to swig 1.3.36, recompiled the above packages and then
recreated my partnership and msycntool groups... So far I'm
synchronising without errors, but as before errors may appear later!

I'll keep you updated.