From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stephan Kulow <coolo@suse.de>, Gerd Hoffmann <kraxel@redhat.com>,
Anthony Liguori <aliguori@amazon.com>
Subject: [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients
Date: Thu, 24 Jul 2014 10:28:05 +0200 [thread overview]
Message-ID: <1406190486-16026-2-git-send-email-kraxel@redhat.com> (raw)
In-Reply-To: <1406190486-16026-1-git-send-email-kraxel@redhat.com>
From: Stephan Kulow <coolo@suse.de>
If the client asks for !incremental frame updates, it has lost its content
so dirty doesn't matter - it has to see the full frame, so setting force_update
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Peter Lieven <pl@kamp.de>
---
ui/vnc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/ui/vnc.c b/ui/vnc.c
index 548588a..06d6ca0 100644
--- a/ui/vnc.c
+++ b/ui/vnc.c
@@ -1878,6 +1878,7 @@ static void framebuffer_update_request(VncState *vs, int incremental,
return;
}
+ vs->force_update = 1;
vnc_set_area_dirty(vs->dirty, width, height, x, y, w, h);
}
--
1.8.3.1
next prev parent reply other threads:[~2014-07-24 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:28 [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Gerd Hoffmann
2014-07-24 8:28 ` Gerd Hoffmann [this message]
2014-07-24 12:30 ` [Qemu-devel] [PULL for-2.1 1/2] fix full frame updates for VNC clients Andreas Färber
2014-07-24 13:45 ` Stephan Kulow
2014-07-24 13:57 ` Andreas Färber
2014-07-24 8:28 ` [Qemu-devel] [PULL for-2.1 2/2] vnc update fix Gerd Hoffmann
2014-07-24 11:48 ` [Qemu-devel] [PULL for-2.1 0/2] vnc: fix two vnc update issues Peter Maydell
2014-07-24 12:20 ` Andreas Färber
2014-07-24 14:10 ` Gerd Hoffmann
2014-07-24 14:22 ` Peter Maydell
2014-07-25 7:45 ` Gerd Hoffmann
2014-07-25 11:52 ` Peter Maydell
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=1406190486-16026-2-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@amazon.com \
--cc=coolo@suse.de \
--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).