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

Joachim Breitner nomeata at debian.org
Wed Mar 25 10:30:18 UTC 2009


Hi,

Am Dienstag, den 24.03.2009, 21:20 +0100 schrieb Sylvain Paré:
> 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'))

Looks the same to me, just a different presentation, due to a different
version of mdbus. Are you trying to parse the output of mdbus?

Greetings,
Joachim
-- 
Joachim "nomeata" Breitner
Debian Developer
  nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
  JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090325/f7a9fad0/attachment.pgp 


More information about the pkg-fso-maint mailing list