feature request: allow dbus path to be configured

[flatsiedatsie]

When running a freshly compiled Shairport-sync with dbus support I get:

warning: could not acquire a Shairport Sync native D-Bus interface "org.gnome.ShairportSync" on the system bus.

The dbus.service on Raspberry Pi OS Trixie is running as:

/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'

Is there a way to configure shairport-sync to use org.freedesktop instead of org.gnome? From looking at the code it seems to be hard-coded. Assuming that's the issue of course.

[mikebrady]

When you install Shairport Sync as a D-Bus service on the system bus for the very first time, it seems that you need to reboot for the service to be permitted. Maybe restarting the dbus daemon might work instead.