• G
    vnc update fix · 63658280
    Gerd Hoffmann 提交于
    We need to remember has_updates for each vnc client.  Otherwise it might
    happen that vnc_update_client(has_dirty=1) takes the first exit due to
    output buffers not being flushed yet and subsequent calls with
    has_dirty=0 take the second exit, wrongly assuming there is nothing to
    do because the work defered in the first call is ignored.
    Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
    Reviewed-by: NPeter Lieven <pl@kamp.de>
    63658280
vnc.c 97.6 KB