From 46eb11051a33fa0b97d4184edf9c53b4207a48c9 Mon Sep 17 00:00:00 2001 From: Pauli Virtanen Date: Sat, 13 Jan 2024 13:18:51 +0200 Subject: [PATCH] bluez5: more informative warning with unknown transports Unknown transports visible in DBus usually belong to a different sound server instance that is talking to BlueZ. Explain this in the warning message that we log, so that people can more easily understand why things are not working. --- spa/plugins/bluez5/bluez5-dbus.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/spa/plugins/bluez5/bluez5-dbus.c b/spa/plugins/bluez5/bluez5-dbus.c index bb6e0a8b3..82a2c85bf 100644 --- a/spa/plugins/bluez5/bluez5-dbus.c +++ b/spa/plugins/bluez5/bluez5-dbus.c @@ -5545,7 +5545,12 @@ static DBusHandlerResult filter_cb(DBusConnection *bus, DBusMessage *m, void *us transport = spa_bt_transport_find(monitor, path); if (transport == NULL) { spa_log_warn(monitor->log, - "Properties changed in unknown transport %s", path); + "Properties changed in unknown transport '%s'. " + "Multiple sound server instances (PipeWire/Pulseaudio/bluez-alsa) are " + "probably trying to use Bluetooth audio at the same time, which can " + "cause problems. The system configuration likely should be fixed " + "to have only one sound server that manages Bluetooth audio.", + path); goto finish; }