I sent the patch on May 16 (http://lists.nongnu.org/archive/html/qemu-
devel/2012-05/msg02373.html). I haven't seen any response.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/806656
Title:
Tight P
cause the TIGHT encoding to be
used even though the client requested TIGHT_PNG.
Signed-off-by: Joel Martin
---
ui/vnc.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/ui/vnc.c b/ui/vnc.c
index be384a5..517d5fa 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -1818,10 +1818,12
** Patch added: "The "Tight PNG" encoding should only be used when
--enable-vnc-png is set."
https://bugs.launchpad.net/bugs/806656/+attachment/2194428/+files/0001-vnc-disable-tight-png-when-not-enable-vnc-png.patch
--
You received this bug notification because you are a member of qemu-
deve
Public bug reported:
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 (--di
