mirror of
				https://gitlab.freedesktop.org/pipewire/pipewire.git
				synced 2025-11-03 09:01:54 -05:00 
			
		
		
		
	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.
This commit is contained in:
		
							parent
							
								
									b59766c3d1
								
							
						
					
					
						commit
						b619616c2a
					
				
					 1 changed files with 1 additions and 1 deletions
				
			
		| 
						 | 
					@ -1949,7 +1949,7 @@ static void transport_state_changed(void *data,
 | 
				
			||||||
	else
 | 
						else
 | 
				
			||||||
		transport_stop(this);
 | 
							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
 | 
							 * If establishing connection fails due to remote end not activating
 | 
				
			||||||
		 * the transport, we won't get a write error, but instead see a transport
 | 
							 * the transport, we won't get a write error, but instead see a transport
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue