qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] update server bits on vnc_update
Date: Tue, 21 Jul 2009 13:19:08 +0200	[thread overview]
Message-ID: <4A65A42C.5050703@redhat.com> (raw)
In-Reply-To: <4A6577A1.9010509@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

On 07/21/09 10:09, Gerd Hoffmann wrote:
> On 07/18/09 06:47, Glauber Costa wrote:
> And while looking at the code I think I've spotted the actual bug: When
> sending a bitblit to the client we do *not* update the local server
> surface. Result is the vnc clients and the vnc servers idea of the
> screen content are not in sync any more. Which in turn will break the
> optimization in (2) and can easily result in a corrupted screen ...

Quick test:  Disabling copyrect should make the screen corruption go 
away then.  Real fix will follow later.

cheers,
   Gerd

[-- Attachment #2: fix --]
[-- Type: text/plain, Size: 529 bytes --]

diff --git a/vnc.c b/vnc.c
index de0ff87..86acfee 100644
--- a/vnc.c
+++ b/vnc.c
@@ -1541,9 +1541,11 @@ static void set_encodings(VncState *vs, int32_t *encodings, size_t n_encodings)
         case VNC_ENCODING_RAW:
             vs->vnc_encoding = enc;
             break;
+#if 0
         case VNC_ENCODING_COPYRECT:
             vs->features |= VNC_FEATURE_COPYRECT_MASK;
             break;
+#endif
         case VNC_ENCODING_HEXTILE:
             vs->features |= VNC_FEATURE_HEXTILE_MASK;
             vs->vnc_encoding = enc;

  reply	other threads:[~2009-07-21 11:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  4:47 [Qemu-devel] [PATCH] update server bits on vnc_update Glauber Costa
2009-07-18 16:20 ` [Qemu-devel] " Anthony Liguori
2009-07-19  7:57 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2009-07-21  8:09 ` [Qemu-devel] " Gerd Hoffmann
2009-07-21 11:19   ` Gerd Hoffmann [this message]
2009-07-21 12:56   ` Stefano Stabellini
2009-07-21 13:16     ` Stefano Stabellini
2009-07-21 13:19     ` Gerd Hoffmann

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=4A65A42C.5050703@redhat.com \
    --to=kraxel@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=glommer@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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).