How to debug dbus access issues?

[tomw]

ok, digging a bit deeper dbus-send was of some help to figure out
whether the method calls work and whether they return the expected
values. So far it works as it should. The underlying problem however
still exists and it seems that it is coming from the python
implementation, for which I don't have an explanation right now:

Python and SessionBus   - works
dbus-send and SystemBus - works
Python and SystemBus    - does not work:

Aug 23 13:23:06 localhost dbus-daemon: [system] Rejected send message, 5
matched rules; type="method_call", sender=":1.67" (uid=500 pid=1818
comm="python) interface="(unset)" member="GetDeviceUUID" error
name="(unset)" requested_reply=0 destination=":1.66" (uid=500 pid=1808
comm="python))

I can call any methods directly from dbus-send, if the methods are
called from Python it fails.

Does anyone have any clue where this may come from?

Thanks,



  

On Mo, 2011-08-22 at 19:22 +0200, tomw wrote:
> Hi,
> 
> running into messages like:
> 
> org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3
> matched rules; type="method_call", ...
> 
> I was wondering what would be the best way to debug this and to find out
> what exactly the 3 matched rules are. dbus-monitor did not provide any
> clue so far, but perhaps I'm just not using it properly.
> 
> Any idea appreciated...
> 
> thanks
> 
>  

-- 
tomw <tomw at ubilix.com>