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.
This commit is contained in:
Pauli Virtanen 2024-01-13 13:18:51 +02:00 committed by Wim Taymans
parent 89d86c73c4
commit ea5ff6b3c1

View file

@ -5557,7 +5557,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;
}