summaryrefslogtreecommitdiffstats
path: root/unix
diff options
context:
space:
mode:
authorPierre Ossman <ossman@cendio.se>2015-09-24 16:24:48 +0200
committerPierre Ossman <ossman@cendio.se>2015-09-24 16:24:48 +0200
commitc88dc805e55cffa7af83ae741b0ffa26aade068e (patch)
tree7a6f115347e7eff521673b790b50e09d23ef8631 /unix
parentff626f823ad627b694e6f4c99717f4d32e637b1d (diff)
downloadtigervnc-c88dc805e55cffa7af83ae741b0ffa26aade068e.tar.gz
tigervnc-c88dc805e55cffa7af83ae741b0ffa26aade068e.zip
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.
Diffstat (limited to 'unix')
-rw-r--r--unix/xserver/hw/vnc/vncBlockHandler.c3
1 files changed, 3 insertions, 0 deletions
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;