bluez-alsa: 4.3.0: org.freedesktop.DBus.Error.NoReply
Hello!
Please read the troubleshooting guide before raising a new issue.
Did that.
Problem
Ok, first of all we talk a totally borked Philips TV that offers playing audio sent to it via bluetooth. I use bluez-alsa for this task for about five years. That is, there were often problems in the past (music stuttering, connection losses), but that improved over time with new bluez-alsa releases and/or Linux kernel changes (first 4.19, then 5.10, now 6.1).
However, since upgrade to bluez-alsa 4.3.0, i can only play music for a couple of minutes, ie, here is complete bluetooth connection establishment / end-of-the-story syslog entry:
Aug 19 17:52:46 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd3: fd(25) ready Aug 19 17:52:46 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd4: fd(25) ready Aug 19 17:56:56 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd5: fd(25) ready Aug 19 17:56:57 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd6: fd(25) ready Aug 19 18:00:50 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd7: fd(25) ready Aug 19 18:00:51 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd8: fd(25) ready Aug 19 18:06:38 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd9: fd(25) ready Aug 19 18:06:38 kent bluetoothd[13142]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd10: fd(25) ready Aug 19 18:12:50 kent bluetoothd[13142]: profiles/audio/media.c:endpoint_reply() Endpoint replied with an error: org.freedesktop.DBus.Error.NoReply
On the application side we then see (of course)
$ ALSAPCM=bt ogg123 -q can-ege_bamyasi.ogg ALSA lib ../../../src/asound/bluealsa-pcm.c:1540:(_snd_pcm_bluealsa_open) Couldn't get BlueALSA PCM: PCM not found ERROR: Cannot open device alsa.
Now, it must be said that the above “fd ready” messages are completely new, at least in this non-unique variant. Ie, the entire August 14th with elder bluez-alsa is
Aug 14 19:30:36 kent /root/bin/zzz.sh: /etc/rc.d/bluetoothd start Aug 14 19:30:36 kent /root/bin/zzz.sh: /etc/rc.d/bluealsa start Aug 14 19:30:36 kent bluetoothd[25786]: Bluetooth daemon 5.77 Aug 14 19:30:36 kent bluetoothd[25786]: Starting SDP server Aug 14 19:30:36 kent bluetoothd[25786]: src/plugin.c:init_plugin() System does not support ccp plugin Aug 14 19:30:36 kent bluetoothd[25786]: Bluetooth management interface 1.22 initialized Aug 14 19:30:36 kent bluetoothd[25786]: Battery Provider Manager created Aug 14 19:30:36 kent bluetoothd[25786]: Adv Monitor Manager created with supported features:0x00000001, enabled features:0x00000001, max number of supported monitors:32, max number of support ed patterns:16 Aug 14 19:30:36 kent bluetoothd[25786]: Failed to set mode: Failed (0x03) Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/sink/1 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/sink/2 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/1 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/2 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/sink/1 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/sink/2 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/source/2 Aug 14 19:30:36 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/source/1 ... Aug 14 19:32:01 kent bluetoothd[25786]: Endpoint registered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/3 Aug 14 19:32:08 kent bluetoothd[25786]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd0: fd(25) ready ... Aug 15 02:51:35 kent bluetoothd[25786]: /org/bluez/hci0/dev_00_F4_8D_33_38_FA/sep1/fd1: fd(25) ready Aug 15 04:44:06 kent /root/bin/zzz.sh: /etc/rc.d/bluealsa stop Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/sink/1 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/sink/2 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/1 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/sink/1 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/sink/2 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/source/2 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/AAC/source/1 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/3 Aug 15 04:44:06 kent bluetoothd[25786]: Endpoint unregistered: sender=:1.266 path=/org/bluez/hci0/A2DP/SBC/source/2 Aug 15 04:44:06 kent /root/bin/zzz.sh: /etc/rc.d/bluetoothd stop
Reproduction steps
That is all i know. (I never deal directly with all the settings, i only use the ALSAPCM environment variable to switch in between devices.) The asound.conf is years old
pcm.!default {
type plug; slave.pcm { @func getenv; vars [ ALSAPCM ]; default "xmix"; }
}
ctl.!default { type hw; card 0; }
pcm.xmix {
type dmix
ipc_key 1024; ipc_gid audio; ipc_perm 0660
slave {
#rate 48000; periods 256; period_time 0; period_size 2048; buffer_size 16384
pcm "hw:0,0" }
}
pcm.bt {
type plug
slave.pcm { type bluealsa; device "00:F4:8D:33:38:FA"; profile "a2dp" }
hint { show on; description "ptv, Frau Antje Bluetooth" }
}
ctl.bt { type bluealsa }
Setup
- the OS distribution and version CRUX-Linux.
- the version of BlueALSA (
bluealsa --version) 4.3.0- the version of BlueZ (
bluetoothd --version) 5.77 (installed since July 13th)- the version of ALSA (
aplay --version) 1.2.12 (alsa-utils, alsa-lib, installed since June 15th)- if self-built from source, please state the branch and commit (
git log -1 --oneline), and the used configure options.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 53 (15 by maintainers)
Commits related to this issue
- Fix potential temporary deadlock in A2DP codec selection procedure. If a dbus client thread locks the codec_id_mtx mutex while Bluez is processing a SetConfiguration request, then that can lead to th... — committed to borine/bluez-alsa by borine 2 years ago
- Fix temporary deadlock in A2DP codec selection If a D-Bus client thread locks the codec_id_mtx mutex while BlueZ is processing a SetConfiguration request, then that can lead to the main thread being ... — committed to borine/bluez-alsa by borine 2 years ago
I’m not sure right now. Will look at it more next week. My pipewire integration relies on wireplumber to disable pipewire’s own bluetooth. I need to establish whether or not wireplumber was running when the problem was occuring. If it was, then the problem was 2 bluealsa clients. If wireplumber was not running, then the problem was 2 applications registered in bluez. So many logs to look through and so little time available!
Agreed - bluealsa should not offer any configuration which is guaranteed to cause denial-of-service!