bluez-alsa: Bluez-Alsa doesn't work on Mint

Hello, I’ve installed Bluez-Alsa, but it seems that it doesn’t work. Always if I try to run it, it appears that:

user@user-Latitude-E5550:~$ zita-a2j -j bt_headphones -d bluealsa:C9:F0:F4:F3:FD:E5 -p 4096 -n 3 -c 2 -L
ALSA lib ../../../src/asound/bluealsa-pcm.c:1313:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA PCM: The name org.bluealsa was not provided by any .service files
Can't open ALSA capture device 'bluealsa:C9:F0:F4:F3:FD:E5'.

I thought the reason could be the way I’ve installed Bluez-Alsa, so I’ve removed everything and used all possibilites from here.

In the .asoundrc.txt file I’ve already added it:

pcm.!default {
    type plug
    slave { pcm "pulse" }
}

pcm.pulse {
    type pulse
}

ctl.mixer0 {
    type hw
    card 0
}



pcm.bt-headphones {
	type bluealsa
	device C9:F0:F4:F3:FD:E5
	profile a2dp
}
ctl.bt-headphones {
	type bluealsa
}

Maybe you’ve some other idea. Many thanks in advance.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 50 (2 by maintainers)

Most upvoted comments

Sorry, I wasn’t very clear: I mean when starting the bluealsa daemon at runtime. So for example in my case I use only SBC and aptX codecs with A2DP profile, and CVSD and mSBC codecs with HFP profile. So my bluealsa command line is:

sudo bluealsa -p a2dp-source -p hfp-ag -p hsp-ag -c sbc -c aptx -c cvsd -c msbc

I think that it is not essential to mention sbc or cvsd as they are included by default anyway, but I like to add them on my systems for clarity.

borine on May 28, 2022

As I’ve already wrote here it was the only way I knew to get Carla managed with Bluetooth devices.

christian179717 on May 21, 2022

omit the -B C9:F0:F4:F3:FD:E5 option - it has nothing to do with bluetooth addresses, and is not needed except in special cases (see the EXAMPLE section of the manual page if you wish to know more about this option). If you can give a brief description of what you want bluealsa to do on your system, I may be able to help with choosing an appropriate configuration.

@Arkq - the GLib-GIO-CRITICAL message is not nice, and not helpful for the user, perhaps bluealsa should sanitize this option before passing to glib ?

borine on May 20, 2022