Bluealsa is old version compiled with debug

Troubleshooting
1

Creating a bug report/issue

[ X] I have searched the existing open and closed issues

Required Information

  • DietPi version | cat /boot/dietpi/.version:

G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=16
G_DIETPI_VERSION_RC=3
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
G_LIVE_PATCH_STATUS[0]=‘applied’
G_LIVE_PATCH_STATUS[1]=‘applied’

  • Distro version | echo $G_DISTRO_NAME $G_RASPBIAN

bookworm 0

  • Kernel version | uname --all

Linux birdQuiz 6.12.34+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.12.34-1+rpt1~bookworm (2025-06-26) aarch64 GNU/Linux

  • Architecture | dpkg --print-architecture

arm64

  • SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)

RPi Zero 2 W (aarch64)

  • Power supply used | (EG: 5V 1A RAVpower)

5V 4.5A Anker

  • SD card used | (EG: SanDisk ultra)

SanDisk Ultra

Additional Information (if applicable)

  • Software title | (EG: Nextcloud)—bluealsa
  • Was the software title installed freshly or updated/migrated?—yes
  • Can this issue be replicated on a fresh installation of DietPi?—yes
    ← If you sent a “dietpi-bugreport”, please paste the ID here →
  • Bug report ID | echo $G_HW_UUID–0deb1e58-d111-44cd-9af2-6b6dffb19101

Steps to reproduce

aplay /usr/share/sounds/alsa/Front_Center.wav
–>also happens in a python script that uses pygame to play sounds

Expected behaviour

Plays sound

Actual behaviour

Plays sound, but also dumps over 20 lines of debug type info to the terminal (running the pi headless)
Here’s the first few lines:

D: bluealsa-pcm.c:532: /org/bluealsa/hci0/dev_27_3A_D2_B7_2D_51/a2dpsrc/sink: Initializing HW
D: bluealsa-pcm.c:567: /org/bluealsa/hci0/dev_27_3A_D2_B7_2D_51/a2dpsrc/sink: FIFO buffer size: 1024 frames
D: bluealsa-pcm.c:581: /org/bluealsa/hci0/dev_27_3A_D2_B7_2D_51/a2dpsrc/sink: Selected HW buffer: 4 periods x 24000 bytes == 96000 bytes
  • bluealsa -V returns v4.0.0
  • Current version is 4.3.1 from august 2024
  • I think that this version was compiled with a debug flag on

Extra details

Trying to upgrade just bluealsa failed with this message:

sudo apt upgrade bluealsa
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package bluealsa is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘bluealsa’ has no installation candidate

Also tried adding options= to /etc/default/bluez-alsa
tried OPTIONS=“–syslog”
also tried OPTIONS=“–loglevel=error”

2

Hello,

you are talking about bluez-alsa-utils. On Debian bookworm the latest version is 4.0.0 (see: https://packages.debian.org/search?keywords=bluez-alsa)
So if you want a newer version you need to ugrade to Debian Trixie or install a newer version manually. But the daemon you have to compile it by yourself.
But this package does not contain the daemon, and your problem is with the daemon. How did you install it? Did you compile it by yourself or what did you do?

Also, if you start it with the verbose flag (bluealsa -v) you will get debug messages. How do you start it?

3

Thanks for your response.
When I looked at the list of files ( Debian -- File list of package bluez-alsa-utils/bookworm/amd64 ), it seems that bluez-alas-utility does contain bluealsa.service etc.
I’m new to this, so I did not compile it myself.

I followed the instructions on this web page to get my Bluetooth speaker working:

How do I upgrade to Trixie and still keep DietPi? Or does someone have a better recommendation?
Thanks in advance

4

Trixie is a Debian version
DietPi is not an own operation system. It’s a set of bash scripts, some automation and some tweaks on top of Debian :wink: There is no conflict between both as they are independent from each other.

did you checked dietpi-config to enable Bluetooth ??

5

Thanks Joulinar.
I may give upgrading a try.
Bluetooth is working, I did use the config program

6

This topic was automatically closed 178 days after the last reply. New replies are no longer allowed.