[pkg-fso-maint] Why the same dbus (fso) interrogation gives a different answer than on SHR?

[Sylvain Paré]

Hi.

I am currently programming an application whitch relies on fso for several
things:
need to know diming time suspend time
gps handling
bluetooth
..

Before implementing dbus call i am testing the answers for my call like:
mdbus -s org.freesmartphone.odeviced
/org/freesmartphone/Device/IdleNotifier/0
org.freesmartphone.Device.IdleNotifier.GetTimeouts

But i receive different answer depending of the target Debian or SHR.

On SHR(unstable - 13-03-2009):
root at om-gta02 ~ $ mdbus -s org.freesmartphone.odeviced
/org/freesmartphone/Device/IdleNotifier/0
org.freesmartphone.Device.IdleNotifier.GetTimeouts
{   'awake':
-1,

    'busy':
-1,

    'idle':
10,

    'idle_dim':
20,

    'idle_prelock':
12,

    'lock':
2,

    'suspend': 0}

aAnd on Debian (uptodate)
debian-gta02:~# mdbus -s org.freesmartphone.odeviced
/org/freesmartphone/Device/IdleNotifier/0
org.freesmartphone.Device.IdleNotifier.GetTimeouts
/org/freesmartphone/Device/IdleNotifier/0: GetTimeouts ->
dbus.Dictionary({dbus.String(u'none'): dbus.Int32(-1), dbus.String(u'busy'):
dbus.Int32(-1), dbus.String(u'lock'): dbus.Int32(2),
dbus.String(u'idle_prelock'): dbus.Int32(12), dbus.String(u'idle'):
dbus.Int32(10), dbus.String(u'suspend'): dbus.Int32(20),
dbus.String(u'awake'): dbus.Int32(-1), dbus.String(u'idle_dim'):
dbus.Int32(20)}, signature=dbus.Signature('si'))

I understand that debian's answer is not normal..
Someone can explain to me the reasons of those differences?
Thanks
regards
Sylvain Paré (aka GarthPS)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090324/38d3297c/attachment.htm