We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
history-pop
history-rm
Originally posted by qxb3 February 8, 2024 Hello! I kinda assume that this actions will emit a events in d-bus but i guess not?
$ dbus-monitor --profile "interface='org.freedesktop.Notifications'" #type timestamp serial sender destination path interface member # in_reply_to sig 1707417506.140839 4294967295 org.freedesktop.DBus :1.73277 /org/freedesktop/DBus org.freedesktop.DBus NameAcquired sig 1707417506.140853 4294967295 org.freedesktop.DBus :1.73277 /org/freedesktop/DBus org.freedesktop.DBus NameLost mc 1707417511.756545 6 :1.73318 :1.39 /org/freedesktop/Notifications org.freedesktop.Notifications GetServerInformation mc 1707417511.757148 7 :1.73318 :1.39 /org/freedesktop/Notifications org.freedesktop.Notifications GetServerInformation mc 1707417511.757979 8 :1.73318 :1.39 /org/freedesktop/Notifications org.freedesktop.Notifications Notify
The text was updated successfully, but these errors were encountered:
@fwsmit I think DBus is well suited for passing signals. For most other things we already pass a signal via DBus, so this just needs to be > added.
@fwsmit
I think DBus is well suited for passing signals. For most other things we already pass a signal via DBus, so this just needs to be > added.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Discussed in #1277
Originally posted by qxb3 February 8, 2024
Hello! I kinda assume that this actions will emit a events in d-bus but i guess not?
The text was updated successfully, but these errors were encountered: