mdbus in FSO under Debian

xaos x xaos at xaositects.com
Mon Aug 18 16:33:00 CEST 2008


mdbus -s with no other arguments returns the expected:

debian-gta02:~# mdbus -s
:1.0
:1.1
:1.2
:1.24
:1.3
:1.4
:1.5
:1.6
:1.8
org.freedesktop.DBus
org.freedesktop.Gypsy
org.freesmartphone.frameworkd
org.freesmartphone.odeviced
org.freesmartphone.oeventd
org.freesmartphone.ogpsd
org.freesmartphone.ogsmd
org.freesmartphone.ophoned
org.freesmartphone.opreferencesd
org.freesmartphone.ousaged
org.pyneo.muxer

and 

debian-gta02:~# mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device org.freesmartphone.GSM.Device.GetInfo
/org/freesmartphone/GSM/Device: GetInfo ->  dbus.Dictionary({dbus.String(u'imei'): dbus.String(u'354651011661834', variant_level=1), dbus.String(u'model'): dbus.String(u'"Neo1973 GTA02 Embedded GSM Modem"', variant_level=1), dbus.String(u'revision'): dbus.String(u'"HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8"', variant_level=1), dbus.String(u'manufacturer'): dbus.String(u'FIC/OpenMoko', variant_level=1)}, signature=dbus.Signature('sv'))

works fine.
However when I try to get a list of methods and signals for /org/freesmartphone/GSM/Device I get the following instead of a list:

debian-gta02:~# mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/GSM/Device
Traceback (most recent call last):
  File "/usr/bin/mdbus", line 399, in <module>
    c.listMethods( busname, objname )
  File "/usr/bin/mdbus", line 191, in listMethods
    data = process_introspection_data( obj.Introspect() )
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 68, in __call__
    return self._proxy_method(*args, **keywords)
  File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in __call__
    **keywords)
  File "/var/lib/python-support/python2.5/dbus/connection.py", line 622, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.AccessDenied: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "(unset)" member "Introspect" error name "(unset)" destination ":1.1")


/etc/dbus-1/system.d/frameworkd.conf seems a tad bit arcane to me so I'm not sure how to edit it to add the permissions. Or maybe I'm just not seeing something that's obvious.

-Tom





More information about the support mailing list