[PROBLEM] Bluetooth Audio output (Transmitter)

[Nachteule]

Yes, I was a bit irritated why you start pulseaudio manually, with my configurations it goes by itself

So I went to the bottom of the matter on a nearly unmodified XBian
There is the file /etc/pulse/client.d/00-disable-autospawn.conf, which prevents the autospawn
Strangely I don't have this file, but I have a file 01-enable-autospawn.conf -> /run/pulseaudio-enable-autospawn in that directory. but I'm sure I never changed anything in there. Probably comes from earlier Debian versions

Anyway if you delete the 00-disable-autospawn.conf or set autospawn=yes pulseaudio starts automatically when Kodi is started


What is also strange is that bluetoothctl on the orginal XBian as user xbian tells me that there are no controllers. so I HAVE to run bluetoothctl as root.
Funny again that this works fine on my development system.
To change this I have to extend the file /etc/dbus-1/system.d/bluetooth.conf, adding

Code:

<policy user="xbian">
    <allow send_destination="org.bluez"/>
    <allow send_interface="org.bluez.Agent1"/>
    <allow send_interface="org.bluez.GattCharacteristic1"/>
    <allow send_interface="org.bluez.GattDescriptor1"/>
    <allow send_interface="org.freedesktop.DBus.ObjectManager"/>
    <allow send_interface="org.freedesktop.DBus.Properties"/>
  </policy>

does the job. Might be a good idea to add this automatically in the future

EDIT:
I'll answer this myself. currently (up to Debian Buster) the user must belong to the group lp or bluetooth so that bluetoothctl can be called as user.
From Debian Bullseye on the user only has to belong to the group bluetooth, which makes more sense.

I noticed that in the default installation the user xbian does not belong to the group bluetooth nor to the group lp.
On my development systems the user xbian is a member of lp as well as bluetooth. Why this is the case I can't say anymore for the life of me