From: Gerd Hoffmann <kraxel@redhat.com>
To: Bug 1087974 <1087974@bugs.launchpad.net>
Cc: Tim Hardeck <thardeck@suse.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1087974] Re: [regression] vnc tight png produces garbled output
Date: Tue, 11 Dec 2012 15:50:13 +0100 [thread overview]
Message-ID: <50C74825.4010800@redhat.com> (raw)
In-Reply-To: <20121211100937.24493.23255.malone@gac.canonical.com>
On 12/11/12 11:09, Tim Hardeck wrote:
> * make sure that qemu is compiled with --enable-vnc-png
>
> * git clone git://github.com/kanaka/noVNC
> * edit include/rfb.js at line 50 and comment out or remove all encodings above "['TIGHT_PNG', -260 ],"
> * open vnc.html in Firefox or Chrome
>
> *apply either my patch to QEMU https://lists.nongnu.org/archive/html
> /qemu-devel/2012-12/msg00869.html or use Websockify
> https://github.com/kanaka/websockify to get Websocket support.
>
> * in case of my patch run QEMU with `-vnc :0,websocket` and connect
> with noVNC to port 5700.
>
> * in case of Websockify run QEMU with `./websockify.py 5900 -- qemu-
> system-x86_64 -vnc :0` and connect to port 5900
Hmm, doesn't reproduce here (using websockify proxy).
--- a/include/rfb.js
+++ b/include/rfb.js
@@ -48,8 +48,8 @@ var that = {}, // Public API methods
// In preference order
encodings = [
- ['COPYRECT', 0x01 ],
- ['TIGHT', 0x07 ],
+// ['COPYRECT', 0x01 ],
+// ['TIGHT', 0x07 ],
['TIGHT_PNG', -260 ],
['HEXTILE', 0x05 ],
['RRE', 0x02 ],
cheers,
Gerd
next prev parent reply other threads:[~2012-12-11 15:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 11:46 [Qemu-devel] [Bug 1087974] [NEW] [regression] vnc tight png produces garbled output Tim Hardeck
2012-12-10 14:23 ` Stefan Hajnoczi
2012-12-10 15:54 ` [Qemu-devel] [Bug 1087974] " Tim Hardeck
2012-12-11 8:57 ` Stefan Hajnoczi
2012-12-11 9:15 ` Gerd Hoffmann
2012-12-11 10:09 ` Tim Hardeck
2012-12-11 14:50 ` Gerd Hoffmann [this message]
2012-12-11 11:11 ` Tim Hardeck
2012-12-11 15:50 ` Tim Hardeck
2012-12-14 12:29 ` Tim Hardeck
2016-11-21 15:45 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50C74825.4010800@redhat.com \
--to=kraxel@redhat.com \
--cc=1087974@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
--cc=thardeck@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).