Tight PNG VNC encoding is sent even when --disable-vnc-png is set

Bug #806656 reported by Joel Martin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Fix Released
Undecided
Unassigned

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.

Revision history for this message
Joel Martin (kanaka) wrote :
Revision history for this message
Corentin Chary (iksaif) wrote :

The patch looks right, maybe you should send it directly to the qemu mailing list.

Revision history for this message
Bruce Rogers (brogers-q) wrote :

Using noVNC and kvm in SLES 11 we have hit this bug as well.

Joel, would you like to send your patch to the qemu mailing list?

Revision history for this message
Joel Martin (kanaka) wrote :

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.

Revision history for this message
Thomas Huth (th-huth) wrote :

Patch had been included here:
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=fe3e7f2dc05225cdd2ba
... so I'm closing this ticket now.

Changed in qemu:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.