This bug was fixed in the package qemu - 1:4.2-3ubuntu6.7
---
qemu (1:4.2-3ubuntu6.7) focal; urgency=medium
* d/p/ubuntu/lp-1882774-*: add newer EPYC processor types (LP: #1887490)
* d/p/u/lp-1896751-exec-rom_reset-Free-rom-data-during-inmigrate-skip.patch:
fix reboot after
Trying to connect using
novnc latest/stable:1.2.0 2020-07-31 (6) 18MB -
as-is failing to connect
Keeping VNC up and refreshing qemu.
Updating to the new qemu from focal proposed (by now resolved the archive
publishing issues we had before this morning).
Get:67
Hello Samuel, or anyone else affected,
Accepted qemu into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/qemu/1:4.2-3ubuntu6.7
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
SRU Template for qemu added and MP linked to fix this in Ubuntu 20.04
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary'
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/qemu/+git/qemu/+merge/391348
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy
** Description changed:
- When running a machine using "-vnc" and the "websocket" option QEMU
- seems to require the subprotocol called 'binary'. This subprotocol does
- not exist in the WebSocket specification. In fact it has never existed
- in the spec, in one of the very early drafts of
I can confirm the test steps mentioned above. In an unchanged scenario a
formerly failing-to-connect case got working when replacing the qemu (on
Focal) in use with a patched one.
Adding an SRU Template for Focal to the bug description ...
--
You received this bug notification because you are a
Repro steps:
$ sudo apt install qemu-system-x86 novnc
/usr/share/novnc
python3 -m http.server
Connect browser to http://:8000/vnc.html
Click "Settings"
Open "advanced"
Open "websocket"
Set port 5700
Clear path
Click "Connect"
And it works ...
Turns out my former check on the
This is in v5.0.0 so fixed in Groovy.
The related noVNC change is in upstream version >=v1.0.0 which correlates with
Ubuntu >=20.04, threfore fixing this in Focals Qemu seems good.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu Focal)
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary' subprotocol
Fixed here:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=c64e1e75381d
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary'
** Changed in: qemu
Status: New => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary' subprotocol
Status in
Ok, thanks!
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary' subprotocol
Status in QEMU:
New
Bug description:
When running
Hi, Samuel
This patch has been viewed by Daniel.
Please see
https://lists.nongnu.org/archive/html/qemu-devel/2019-12/msg00264.html
However, Daniel has not sent a PR which includes this patch.
Thanks.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Did anyone at QEMU get a chance to look at that patch?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket proxy requires non-standard 'binary' subprotocol
Status in
I have sent a patch about this problem.
Please see https://lists.nongnu.org/archive/html/qemu-
devel/2019-11/msg03924.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC
Thank you for your response, Daniel!
Do you think this is something you will have the opportunity to look at
soon?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1849644
Title:
QEMU VNC websocket
It isn't mandatory to use a standardized subprotocol, all that's
required is that the client & server agree
https://developer.mozilla.org/en-
US/docs/Web/HTTP/Protocol_upgrade_mechanism
"The subprotocols may be selected from the IANA WebSocket Subprotocol
Name Registry or may be a custom
18 matches
Mail list logo
