qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for 2.7] ui: fix refresh of VNC server surface
Date: Tue, 16 Aug 2016 17:30:07 +0100	[thread overview]
Message-ID: <20160816163007.GL25115@redhat.com> (raw)
In-Reply-To: <1471364482-6649-1-git-send-email-berrange@redhat.com>

On Tue, Aug 16, 2016 at 05:21:22PM +0100, Daniel P. Berrange wrote:
> In previous commit
> 
>   commit c7628bff4138ce906a3620d12e0820c1cf6c140d
>   Author: Gerd Hoffmann <kraxel@redhat.com>
>   Date:   Fri Oct 30 12:10:09 2015 +0100
> 
>     vnc: only alloc server surface with clients connected
> 
> the VNC server was changed so that the 'vd->server' pixman
> image was only allocated when a client is connected.
> 
> Since then if a client disconnects and then reconnects to
> the VNC server all they will see is a black screen until
> they do something that triggers a refresh. On a graphical
> desktop this is not often noticed since there's many things
> going on which cause a refresh. On a plain text console it
> is really obvious since nothing refreshes frequently.
> 
> The problem is that the VNC server didn't update the guest
> dirty bitmap, so still believes its server image is in sync
> with the guest contents.
> 
> To fix this we must explicitly mark the entire guest desktop
> as dirty after re-creating the server surface. Move this
> logic into vnc_update_server_surface() so it is guaranteed
> to be call in all code paths that re-create the surface
> instead of only in vnc_dpy_switch()
> 
> Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> 
> NB This should go into 2.5 & 2.6 stable branches too
> 
>  ui/vnc.c | 17 +++++++++--------
>  1 file changed, 9 insertions(+), 8 deletions(-)

And next time I'll make sure I committed all outstanding
chunks before sending the email :-)

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

      parent reply	other threads:[~2016-08-16 16:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16 16:21 [Qemu-devel] [PATCH for 2.7] ui: fix refresh of VNC server surface Daniel P. Berrange
2016-08-16 16:27 ` no-reply
2016-08-16 16:30 ` Daniel P. Berrange [this message]

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=20160816163007.GL25115@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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).