You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"busctl monitor service" seems to display all messages regardless of service argument.
Generally, if a service is specified, busctl monitor shows messages to or from this peer, identified by its well-known or unique name. Otherwise, it shows all messages on the bus.
However, even though a service is specified with busctl by dbus-broker, it seems to display all messages on the bus.
It looks like #369 is not relevant to this.
I need to be able to monitor only the services I want to monitor, but I can't seem to do that. Did I do something wrong, or does the code need to be fixed?
The text was updated successfully, but these errors were encountered:
Have a look at #232, this is an unfortunate situation but we have been unaware of any proper solution to fix this. dbus-daemon silently drops messages when you perform such destination matches, which we consider unsuitable. Hence, you see a catch-all match which just returns you all information.
There are ideas how to fix this, but they will require specification adjustments. I am unaware of anyone working on this, though.
"busctl monitor service" seems to display all messages regardless of service argument.
Generally, if a service is specified, busctl monitor shows messages to or from this peer, identified by its well-known or unique name. Otherwise, it shows all messages on the bus.
However, even though a service is specified with busctl by dbus-broker, it seems to display all messages on the bus.
It looks like #369 is not relevant to this.
I need to be able to monitor only the services I want to monitor, but I can't seem to do that. Did I do something wrong, or does the code need to be fixed?
The text was updated successfully, but these errors were encountered: