summary refs log tree commit diff stats
path: root/results/classifier/deepseek-2-tmp/output/vnc/806656
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/vnc/806656')
-rw-r--r--results/classifier/deepseek-2-tmp/output/vnc/8066568
1 files changed, 0 insertions, 8 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/vnc/806656 b/results/classifier/deepseek-2-tmp/output/vnc/806656
deleted file mode 100644
index d69e144c..00000000
--- a/results/classifier/deepseek-2-tmp/output/vnc/806656
+++ /dev/null
@@ -1,8 +0,0 @@
-
-Tight PNG VNC encoding is sent even when --disable-vnc-png is set
-
-This bug exists in 0.14.1 and also in 9312805d33e8b (Jun 17, 2011) in the master git repo.
-
-The "Tight PNG" encoding is a derivative of the "Tight" encoding that replaces zlib encoded rects with PNG encoded data instead. However, when the "Tight PNG" encoding is disabled (--disable-vnc-png), the server will send frame buffer updates that are marked as "Tight PNG" but in fact contain zlib encoded regions (i.e. it's really "tight" protocol).
-
-The "Tight PNG" encoding should only be used when --enable-vnc-png is set.
\ No newline at end of file