Discussion:
[Synce-devel] [SynCE-WindowsMobile5] synce and dbus-python
Dr J A Gow
2007-10-08 22:37:52 UTC
Permalink
I can't debug the dbus-python-0.80.2 problem yet. This is simply
because
for various reasons I can't disturb the base configuration of my
development box at the moment. When the next stable openSUSE release
comes in with 0.80.2 or higher, I'll attack it.
What are the symptoms of this dbus-python problem? I can't seem to find
out the exact problem... or my previous emails on it!
At last I am seeing this error with the new SuSE 10.3. Now I can debug
it :)

Will let you know the results soon.

John.
Iain Buchanan
2007-10-09 01:31:58 UTC
Permalink
Post by Dr J A Gow
I can't debug the dbus-python-0.80.2 problem yet. This is simply
because
for various reasons I can't disturb the base configuration of my
development box at the moment. When the next stable openSUSE release
comes in with 0.80.2 or higher, I'll attack it.
What are the symptoms of this dbus-python problem? I can't seem to find
out the exact problem... or my previous emails on it!
At last I am seeing this error with the new SuSE 10.3. Now I can debug
it :)
Will let you know the results soon.
woohoo!!

:)
--
Iain Buchanan <iaindb at netspace dot net dot au>

You can't depend on me all your lives. You have to learn that there's a
little Homer Simpson in all of us.

-- Homer Simpson
Homer Defined
Dr J A Gow
2007-10-10 13:24:46 UTC
Permalink
Post by Iain Buchanan
Post by Dr J A Gow
I can't debug the dbus-python-0.80.2 problem yet. This is simply
because
for various reasons I can't disturb the base configuration of my
development box at the moment. When the next stable openSUSE release
comes in with 0.80.2 or higher, I'll attack it.
What are the symptoms of this dbus-python problem? I can't seem to find
out the exact problem... or my previous emails on it!
At last I am seeing this error with the new SuSE 10.3. Now I can debug
it :)
Will let you know the results soon.
woohoo!!
:)
Aw, hell! I _thought_ I had seen this error. However, when I went to
debug the problem the next day, it had disappeared!

Works here consistently with the following versions (taken from SuSE
RPMs):

dbus-1-1.0.2-59
dbus-1-python-0.82.0-28

Note that this is a 64 bit system. Will be installing on a 32 bit system
soon so I will see if there is any difference.

Of course, it is possible that a fix crept in between 0.80.2 and 0.82.0.
I am guessing that this is probably very likely. There is clearly no
problem with our (SynCE) code as it is certainly using the dbus method
call correctly. Such a catastrophic problem would certainly have shown
up elsewhere and probably been detected by the dbus developers.

Any chance you could try these later versions of dbus/dbus-python?

John.

Loading...