mirror of
				https://gitlab.freedesktop.org/pipewire/pipewire.git
				synced 2025-11-03 09:01:54 -05:00 
			
		
		
		
	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:
		
							parent
							
								
									c0716675e8
								
							
						
					
					
						commit
						46eb11051a
					
				
					 1 changed files with 6 additions and 1 deletions
				
			
		| 
						 | 
					@ -5545,7 +5545,12 @@ static DBusHandlerResult filter_cb(DBusConnection *bus, DBusMessage *m, void *us
 | 
				
			||||||
			transport = spa_bt_transport_find(monitor, path);
 | 
								transport = spa_bt_transport_find(monitor, path);
 | 
				
			||||||
			if (transport == NULL) {
 | 
								if (transport == NULL) {
 | 
				
			||||||
				spa_log_warn(monitor->log,
 | 
									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;
 | 
									goto finish;
 | 
				
			||||||
			}
 | 
								}
 | 
				
			||||||
 | 
					
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue