mandeepsandhu.chd at gmail.com
Wed Oct 6 03:14:05 PDT 2010
> Your dbus-monitor logs don't show the D-Bus message sent by dbus-send,
> probably because you use the system bus and by default, eavesdropping
> is disabled. Do you use the system bus intentionally? You could use the
Yes, I'm intentionally using the system bus. I'm setting this up so
that NetworkManager can be used on my platform. But I'll be setting up
the session bus too, later...
> session bus which has eavesdropping enabled by default.
> For debugging purpose, you can edit your system.conf to allow
> 1. replace the policy section by:
> <policy context="default">
> <!-- Allow everything to be sent -->
> <allow send_destination="*" eavesdrop="true"/>
> <!-- Allow everything to be received -->
> <allow eavesdrop="true"/>
> <!-- Allow anyone to own anything -->
> <allow own="*"/>
> <!-- XXX: Allow all users to connect -->
> <allow user="*"/>
> 2. Remove the includedir line:
> Then, eavesdropping with dbus-monitor should work correctly.
Thanks, will try this.
>> * Why is the 'dest' field null when I'm setting it to
> The NameOwnerChanged signals is not what is sent by your
> command ../dbus-send but by dbus-daemon itself, so what you specify in
> --dest does not change anything here. D-Bus signals in general are not
> sent to a specific destination (i.e. the destination is "null") but to
> any peers who want to listen to them with match rules.
Thanks Alban. I need to read up a lot more on DBUS for sure!
> dbus mailing list
> dbus at lists.freedesktop.org
More information about the dbus