From b619616c2a729703ba268d9976c38a59690b11fd Mon Sep 17 00:00:00 2001 From: Pauli Virtanen Date: Tue, 18 Apr 2023 22:26:18 +0300 Subject: [PATCH] bluez5: media-sink: don't fail A2DP duplex sink if remote idles Don't emit node error for A2DP duplex sink channel, or when BAP server. These can occur under normal conditions (remote side suspends transport), and are not errors. --- spa/plugins/bluez5/media-sink.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spa/plugins/bluez5/media-sink.c b/spa/plugins/bluez5/media-sink.c index a5def9502..efb7ef9a2 100644 --- a/spa/plugins/bluez5/media-sink.c +++ b/spa/plugins/bluez5/media-sink.c @@ -1949,7 +1949,7 @@ static void transport_state_changed(void *data, else transport_stop(this); - if (state < SPA_BT_TRANSPORT_STATE_ACTIVE && was_started) { + if (state < SPA_BT_TRANSPORT_STATE_ACTIVE && was_started && !this->is_duplex && this->is_output) { /* * If establishing connection fails due to remote end not activating * the transport, we won't get a write error, but instead see a transport