Xenial has reached "End of Standard Support" and hence I am marking
those tasks as "Won't Fix". Thank you!
** Changed in: qemu (Ubuntu Xenial)
Status: Incomplete => Won't Fix
** Changed in: novnc (Ubuntu Xenial)
Status: New => Won't Fix
--
You received this bug notification becaus
Trying to clean some old issue I've removed the Bionic tasks where this
should be working fine so there is no task to be done on that release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689488
Tit
** No longer affects: qemu (Ubuntu Bionic)
** No longer affects: novnc (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689488
Title:
vnc console accepts only 8 characters
To manage
** Tags removed: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689488
Title:
vnc console accepts only 8 characters
To manage notifications about this bug go to:
https://bugs.launchpad.
novnc 1.1 is in disco and later at least.
** Also affects: novnc (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: novnc (Ubuntu Yakkety)
** Changed in: qemu (Ubuntu Xenial)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: qemu (Ubuntu Yakket
Hi Christian,
Thanks a lot for all your testing, really appreciated.
Actually similar issue still exists on our platforms with novnc 0.6.2 and
latest websockify.
We work on upgrading to novnc 1.1.0 recently.
We find this issue does not exist any more after upgrading to novnc 1.1.0.
Now we confir
Thanks for your feedback, so to confirm
You have
- Server A
- running VMs with "normal" VNC console e.g. on 590*
- novnc server linking the VM vnc sessions and making them available on e.g.
6800
like novnc ./utils/launch ...
- System B
- accessing A:6800 via local novnc
- Here for bet
Hi Christian,
Thanks for your effort on this issue.
We have a novnc server running and access the console of vms on other
servers via the novnc server.
I also added a method in novnc to send a string via keyevent. The code
looks like
+sendString : function(str) {
+if (this._
Well, to some extend today I accidentally found that the default sdl frontent
might have this issue as well.
If you start qemu by cmdline and e.g. just give it an ISO.
You need to slow that X11 connection down e.g. by running this via X11
forwarding across an ocean.
So the handling gets sloggy, w
Got feedback from Yang, trying that later today.
Quote of the reply mail:
"Hi Christian,
You could use novnc to send a bulk of text to the VM’s vnc console in one
request.
https://github.com/novnc/noVNC";
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Hi,
I'm currently cleaning up dormant virtualization stack bugs.
Lets take the easy step first, Yakkety is EOL so this is Won't Fix.
As asked in comment #1 I'd need a bit more help on how to reproduce as
we will need steps to reproduce to verify the SRU [1] as part of the
process to fix issues in
** Changed in: qemu (Ubuntu Yakkety)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1689488
Title:
vnc console accepts only 8 characters
To manage notifications a
Thanks for reporting that issue and your help to make Ubuntu better.
I agree on the versions and commits that are referred.
Thereby Xenial and Yakkety are the versions that would need an SRU.
I don't know how fast I get to that, also it is hard for me to realize the
importance of "only accept 8
13 matches
Mail list logo
