Public bug reported:
Description of problem
-
In my latest topic, I reported a bug relate to QEMU's websocket:
https://bugs.launchpad.net/qemu/+bug/1718964
It has been fixed but someone mentioned that he met the same problem when using
QEMU with a standalone websocket pro
** Attachment added: "Used with QEMU.jpg"
https://bugs.launchpad.net/qemu/+bug/1725707/+attachment/4982276/+files/Used%20with%20QEMU.jpg
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1725707
Titl
** Attachment added: "Used with other VNC servers.jpg"
https://bugs.launchpad.net/qemu/+bug/1725707/+attachment/4982277/+files/Used%20with%20other%20VNC%20servers.jpg
** Description changed:
Description of problem
-
In my latest topic, I reported a bug relate to
Public bug reported:
Description of problem
-
When VNC is connected to QEMU via websocket over a low speed network
(e.g. 300KB/S Wide Area Network), and there is a lot of frame buffer
update, the VNC Client will get stuck, the cursor is almost impossible
to move, which may
