summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/806656
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/806656
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/806656')
-rw-r--r--results/scraper/launchpad-without-comments/8066567
1 files changed, 7 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/806656 b/results/scraper/launchpad-without-comments/806656
new file mode 100644
index 000000000..6064e1c26
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/806656
@@ -0,0 +1,7 @@
+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