Sniffing the system bus for specific destination calls

Alan Martinovic <alan.martinovic-+NedCK/[email protected]>
Newsgroups gmane.comp.freedesktop.dbus
Message-ID <CAOT_U5b=K0egDSmChDcg-ZHpuFxQfFA40FjPHj30JDQtHX3NMw@mail.gmail.com>
Hi,
am trying to listen to method_calls directed towards org.bluez and
am experiencing issues in filtering what I actually see while sniffing
the system bus.

Here are commands for both busctl and dbus-monitor that
sniff all method_calls:

busctl monitor --match "type='method_call'" > all-method-calls
    ### CONTAINS THIS ENTRY
    > Type=method_call  Endian=l  Flags=0  Version=1  Priority=0 Cookie=22
        Sender=:1.185  Destination=:1.159
Path=/org/bluez/hci0/dev_CD_68_55_48_A7_C9
Interface=org.bluez.Device1  Member=Connect
        UniqueName=:1.185
        MESSAGE "" {
        };

dbus-monitor --system "type='method_call'" > all-method-calls-dbus-monitor
    ### CONTAINS THIS ENTRY
    method call time=1524738518.286017 sender=:1.188 ->
destination=:1.159 serial=22
path=/org/bluez/hci0/dev_CD_68_55_48_A7_C9;
interface=org.bluez.Device1; member=Connect


So both contain the entry destination=:1.159 which is the unique name for
org.bluez. So far so good.


Now I want to limit that to contain only calls for the
particular destination:

busctl monitor --match "type='method_call', destination=':1.159',
eavesdrop='false'"
# Lists nothing when called

dbus-monitor --system "type='method_call', destination=':1.159',
eavesdrop='true'"
# Lists nothing when called


However neither results in matches, that obviously exist with a broader filter.
Removing eavesdrop='true' or setting it to false had no influence on the result.

The version in question is:

dbus-daemon --version
    D-Bus Message Bus Daemon 1.10.20


Any hints on whet the issue might be?
_______________________________________________
dbus mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dbus
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.