[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-10-12 Thread Launchpad Bug Tracker
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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-30 Thread Christian Ehrhardt 
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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-29 Thread Robie Basak
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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-25 Thread Christian Ehrhardt 
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849644 Title: QEMU VNC websocket proxy requires non-standard 'binary'

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-25 Thread Launchpad Bug Tracker
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849644 Title: QEMU VNC websocket proxy

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt 
** 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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt 
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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt 
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

[Bug 1849644] Re: QEMU VNC websocket proxy requires non-standard 'binary' subprotocol

2020-09-24 Thread Christian Ehrhardt 
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)