From c88dc805e55cffa7af83ae741b0ffa26aade068e Mon Sep 17 00:00:00 2001 From: Pierre Ossman Date: Thu, 24 Sep 2015 16:24:48 +0200 Subject: [PATCH] Make sure fallback block handler remains enabled Commit f8e3b34 introduced a regression where the fallback write block handler would cease working after the first time it was called, potentially stalling writes. --- unix/xserver/hw/vnc/vncBlockHandler.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/unix/xserver/hw/vnc/vncBlockHandler.c b/unix/xserver/hw/vnc/vncBlockHandler.c index c9a7428d..4e444783 100644 --- a/unix/xserver/hw/vnc/vncBlockHandler.c +++ b/unix/xserver/hw/vnc/vncBlockHandler.c @@ -104,6 +104,9 @@ static void vncWriteBlockHandlerFallback(OSTimePtr timeout) FD_ZERO(&fallbackFds); vncWriteBlockHandler(&fallbackFds); + // vncWriteBlockHandler() will clear this, so we need to restore it + needFallback = TRUE; + if (!XFD_ANYSET(&fallbackFds)) return; -- 2.39.5