-
Notifications
You must be signed in to change notification settings - Fork 80
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 signals by arguments does not work #367
Comments
This was referenced Jun 4, 2024
This looks like a bug in dbus-broker. In particular: https:/bus1/dbus-broker/blob/main/src/bus/match.c#L425 This uses |
Yikes, that's a bug indeed. Mea culpa! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, for some reason i am not able to get signal filtering by argument value to work.
Reproducer
# dbus-monitor --system "arg3='done'"
# systemctl restart polkit
Expected result
signal time=1716466590.572778 sender=:1.0 -> destination=(null destination) serial=5066 path=/org/freedesktop/systemd1; interface=org.freedesktop.systemd1.Manager; member=JobRemoved
uint32 4996
object path "/org/freedesktop/systemd1/job/4996"
string "polkit.service"
string "done"
Actual result
None
Context:
I am developing daemon that is listening for JobRemoved signal of systemd and i would like to receive only signal related to a service i am watching. I am using dbus-python but so far i am not able to get filtering by argument to work.
Am i missing something or is it possible that there is a bug?
Environment i am using is Fedora Rawhide.
dbus-broker-36-2
Thanks for any help.
The text was updated successfully, but these errors were encountered: