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 (--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.
** Affects: qemu
Importance: Undecided
Status: New
--
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 PNG VNC encoding is sent even when --disable-vnc-png is set
Status in QEMU:
New
Bug description:
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/806656/+subscriptions
