`seat_execute_command` was incorrectly setting `config->handler_context.seat` before calling `execute_command`. Since `execute_command` was being called with a `NULL` seat argument, `execute_command` was setting `config->handler_context.seat` to the default seat. This resulted in all bindings being executed on the default seat and causing undesired behavior for devices on other seats.master
							parent
							
								
									da8f24de1d
								
							
						
					
					
						commit
						fdc262d402
					
				
					Loading…
					
					
				
		Reference in new issue