Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filtering with busctl monitor doesn't work #381

Open
MatthewSukyoung opened this issue Nov 20, 2024 · 1 comment
Open

Filtering with busctl monitor doesn't work #381

MatthewSukyoung opened this issue Nov 20, 2024 · 1 comment

Comments

@MatthewSukyoung
Copy link

"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?

@dvdhrm
Copy link
Member

dvdhrm commented Nov 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants