From 84a6f38ea6d31a3ef23d92f34cff75c9cea405aa Mon Sep 17 00:00:00 2001 From: Wim Taymans Date: Fri, 21 Apr 2023 16:28:01 +0200 Subject: [PATCH] jack: on do shutdown on EPIPE There are core errors that should not trigger a shutdown, like invalid or destroyed proxy replies. Only do shutdown when we get EPIPE, which is when the server is stopped. See #3070 --- pipewire-jack/src/pipewire-jack.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pipewire-jack/src/pipewire-jack.c b/pipewire-jack/src/pipewire-jack.c index da0a2c99d..7a1e18ad6 100644 --- a/pipewire-jack/src/pipewire-jack.c +++ b/pipewire-jack/src/pipewire-jack.c @@ -850,7 +850,7 @@ static void on_error(void *data, uint32_t id, int seq, int res, const char *mess if (id == PW_ID_CORE) { client->last_res = res; - if (!client->destroyed) + if (res == -EPIPE && !client->destroyed) do_callback(client, shutdown_callback, client->shutdown_arg); } pw_thread_loop_signal(client->context.loop, false);