I hardly had any success using a dbus-dependent tool over ssh (for example
pactl -- pulseaudio command line interface -- that selects audio output).
I know how to manually export the session's DBUS address to
DBUS_SESSION_BUS_ADDRESS, but still almost any application fails with messages like
connection refused at pa_context_new().
This, sadly, fits well all the reservations against dbus, kdbus (and systemd)...
So what steps are actually required to make any application depending on DBUS run over ssh just as it would from the desktop session?
Is there any non flaky, non error-prone way to get the bus address without relying on screen-long scripts?
What else is required -- appart from the address -- to allow connection?