vaiojasard
New Member
HW: Raspberry Pi 4 Model B Rev 1.2
OS: Dietpi (Debian GNU/Linux 12 (bookworm))
Others: headless, no X
dietpi@HachimanII:~$ dpkg -l | grep bluez
ii bluez 5.66-1+rpt1+deb12u2 arm64 Bluetooth tools and daemons
ii bluez-firmware 1.2-9+rpt3 all Firmware for Bluetooth devices
My "final" use case is to use a BT speaker as the audio sink for a daemon running as a specific user (ringy).
Due to the fact that I was (and still I'm) a newbie, I decided to take baby steps. So I decided to make the speaker work under the dietpi user.
What I did:
After that, I decided to do the same for user ringy (the one that is running my daemon)
Basically, I reproduced the steps above for user ringy (disabled and masked the services for dietpi)
The problem I'm facing is that every time I try to pair the BT speaker (launching a bluetoothctl session) with user ringy, the pairing and the connection (triggered automatically upon pairing)
seems to work as expected (as per bluetoothctl output), just to be dropped shortly after.
The error (journalctl) is:
Aug 08 22:02:05 HachimanII bluetoothd[292]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for <BT Speaker MAC>: Protocol not available
Has someone experienced a similar error?
Thanks!
Best
OS: Dietpi (Debian GNU/Linux 12 (bookworm))
Others: headless, no X
dietpi@HachimanII:~$ dpkg -l | grep bluez
ii bluez 5.66-1+rpt1+deb12u2 arm64 Bluetooth tools and daemons
ii bluez-firmware 1.2-9+rpt3 all Firmware for Bluetooth devices
My "final" use case is to use a BT speaker as the audio sink for a daemon running as a specific user (ringy).
Due to the fact that I was (and still I'm) a newbie, I decided to take baby steps. So I decided to make the speaker work under the dietpi user.
What I did:
- loginctl enable-linger dietpi
- created a per-user daemon to spin up a session dbus (basically, executes /usr/bin/dbus-daemon --session --address=unix
ath=/run/user/999/bus --nofork --nopidfile) - created a per-user daemons to launch pipewire and wireplumber
- paired/trusted/connected the BT speaker using bluetoothctl
- tested it with aplay (succesfully played audio)
- all this was done for dietpi user
After that, I decided to do the same for user ringy (the one that is running my daemon)
Basically, I reproduced the steps above for user ringy (disabled and masked the services for dietpi)
The problem I'm facing is that every time I try to pair the BT speaker (launching a bluetoothctl session) with user ringy, the pairing and the connection (triggered automatically upon pairing)
seems to work as expected (as per bluetoothctl output), just to be dropped shortly after.
The error (journalctl) is:
Aug 08 22:02:05 HachimanII bluetoothd[292]: src/service.c:btd_service_connect() a2dp-sink profile connect failed for <BT Speaker MAC>: Protocol not available
Has someone experienced a similar error?
Thanks!
Best
