| commit | 9e1632ad07ca49de99da4bb231e9e2f22f2d8df5 | |
| author | Gerd Hoffmann <kraxel@redhat.com> | |
| Tue, 12 Jan 2021 13:41:19 +0000 (12 14:41 +0100) | ||
| committer | Gerd Hoffmann <kraxel@redhat.com> | |
| Fri, 15 Jan 2021 10:22:43 +0000 (15 11:22 +0100) | ||
| tree | 001defe835130ec929bae856d82d1a5a20956426 | treesnapshot (tar.gz zip) |
| parent | b3c2de9cd5bc0023901e7a4d568dfc5152b6cc4a | commitdiff |
vnc: move initialization to framebuffer_update_request
qemu sends various state info like current cursor shape to newly connected
clients in response to a set_encoding message. This is not correct according
to the rfb spec. Send that information in response to a full (incremental=0)
framebuffer update request instead. Also send the resize information
unconditionally, not only in case of an actual server-side change.
This makes the qemu vnc server conform to the spec and allows clients to
request the complete vnc server state without reconnect.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-id: 20210112134120.2031837-3-kraxel@redhat.com
qemu sends various state info like current cursor shape to newly connected
clients in response to a set_encoding message. This is not correct according
to the rfb spec. Send that information in response to a full (incremental=0)
framebuffer update request instead. Also send the resize information
unconditionally, not only in case of an actual server-side change.
This makes the qemu vnc server conform to the spec and allows clients to
request the complete vnc server state without reconnect.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Message-id: 20210112134120.2031837-3-kraxel@redhat.com
| ui/vnc.c | diffblobblamehistory |