From f641e4ecb3e6d1788d01929dc4be87c73d937829 Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Tue, 26 Apr 2022 20:32:25 +0200 Subject: [PATCH] jack: don't wait for activation update We could do an invoke, wait, then the process could do a jack_connect() , do_sync and we deadlock. it's probably better to not wait for completion. --- pipewire-jack/src/pipewire-jack.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/pipewire-jack/src/pipewire-jack.c b/pipewire-jack/src/pipewire-jack.c index dcaae2c5a..a08a40274 100644 --- a/pipewire-jack/src/pipewire-jack.c +++ b/pipewire-jack/src/pipewire-jack.c @@ -1641,8 +1641,7 @@ static int update_driver_activation(struct client *c) link = find_activation(&c->links, c->driver_id); c->driver_activation = link ? link->activation : NULL; pw_data_loop_invoke(c->loop, - do_update_driver_activation, SPA_ID_INVALID, NULL, 0, - !c->data_locked, c); + do_update_driver_activation, SPA_ID_INVALID, NULL, 0, false, c); install_timeowner(c); return 0;