Audacious continuously floods dbus with PropertiesChanged signal
Added by el boulangero over 10 years ago
Hello there,
While doing some dbus monitoring to kill time, I noticed that Audacious, when playing, floods dbus a little bit with that:
$ dbus-monitor type='signal',sender=org.mpris.MediaPlayer2.audacious
signal sender=:1.10 -> dest=(null destination) serial=5858 path=/org/mpris/MediaPlayer2; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged
string "org.mpris.MediaPlayer2.Player"
array [
dict entry(
string "Position"
variant int64 2545000
)
]
array [
]
This is a signal indicating that the position in the track changed, so it's quite normal. But Audacious sends it around 5 times per second.
It does no harm, but isn't that a little bit too much ? Or is it intended to be like that ?
Replies (3)
RE: Audacious continuously floods dbus with PropertiesChanged signal - Added by el boulangero over 10 years ago
From the MPRIS doc, no signal should be emitted when the property Position changes:
[[http://specifications.freedesktop.org/mpris-spec/latest/Player_Interface.html#Property:Position]]
RE: Audacious continuously floods dbus with PropertiesChanged signal - Added by John Lindgren over 10 years ago
It isn't possible to disable PropertiesChanged with GDBus; see https://bugzilla.gnome.org/show_bug.cgi?id=674913.
RE: Audacious continuously floods dbus with PropertiesChanged signal - Added by el boulangero over 10 years ago
Hi John,
I was aware of that '<annotation>' stuff, I saw it working in some Python code, and I thought it had just been omitted somewhere in Audacious code.
Thanks for the explanations, and long life to Audacious !