Error on startup: /usr/bin/bluealsa: Couldn't acquire D-Bus name: org.bluealsa
See original GitHub issueI had this working fine until the last couple of days. Now I get the following error when the container starts:
Setting volume to 100%
Restarting bluetooth service
Bluetooth agent registered
/usr/bin/bluealsa: Couldn't acquire D-Bus name: org.bluealsa
Device is discoverable as "balenaSound"
/usr/bin/bluealsa-aplay: Couldn't get BlueALSA PCM list: The name org.bluealsa was not provided by any .service files
There was a Balena image rebuild, but no relevant code changes as far as I’m aware. Deploying an older release avoids the error.
Any ideas?
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Not able to run bluealsa properly: Couldn't acquire D-Bus name
If the file is present, then possibly the system dbus needs to be restarted - a reboot appears to be the most reliable...
Read more >raspbian - bluealsa: Couldn't acquire D-Bus name: org.bluealsa
If one tries to run second instance, it will fail with the "Couldn't acquire D-Bus name: org.bluealsa" error message.
Read more >Raspberry Pi: bluealsa: Couldn't acquire D-Bus name - YouTube
Raspberry Pi: bluealsa : Couldn't acquire D-Bus name : org.bluealsaHelpful? Please support me on Patreon: ...
Read more >Bluetooth and BlueALSA in Raspberry Pi OS Lite (November ...
It is necessary to wait until the device is discovered, which means than scanning must be enabled. [bluetooth]# scan on Failed to start...
Read more >[SOLVED] Cannot connect to my RPI as a bluetooth headset ...
the problem is that pulseaudio does not work on the Rpi, ... Couldn't get BlueALSA PCM list: The name org.bluealsa was not provided...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks @pwt, it is working fine now.
As I suspected, the problem is due to the switch to Buster from Stretch. If you use Stretch, everything works as before. The first line in Dockerfile.template needs to be changed as follows:
Probably best to revert back to Stretch while the Buster bugs/changes are worked out. I’m hitting Buster issues in a number of different areas.
I’ll create a PR.