Description of problem: Some keys, e.g. "|" or "@" can not be submitted to the vm via novnc when useing e.g. a german keyboard layout, which is crucial for some commands, especially when you want to debug a vm on the console level. please note that the list of missing chars is not complete, I will submit the complete list, once I tested all characters. Version-Release number of selected component (if applicable): this should not work in all ovirt versions How reproducible: always Steps to Reproduce: 1.fire a vm up with novnc and german (other languages might also be affected) keyboard layout for vnc for this vm 2. try to type some chars which are not that common 3. Actual results: can't use useful stuff like pipes or "@" Expected results: can use all keys Additional info: I know this is a problem with the upstream project novnc and with the used browser (firefox) (in chrome some other keys don't work, as far as I remember) See upstream issues here: https://github.com/kanaka/noVNC/issues/21 https://bugzilla.mozilla.org/show_bug.cgi?id=809410 So I don't expect redhat/ovirt devs to solve it themselves, but maybe you can assist upstream in solving this? regarding firefox: they don't even seem to recognize the problem, I guess, because they don't know about the impact yet, so maybe we as a community can make some progress by adding additional information to the bug reports where possible, or maybe even propose fixes, so ovirt and in the end rhev can profit from it (and the users of course)! Thanks
waiting on next release of noVNC
I just wanted to updated that there is a new novnc release 0.5.1 however this still does not fix all of the outstanding bugs regarding special characters (afaik). I didn't test it myself, though.
(In reply to Sven Kieske from comment #2) > I just wanted to updated that there is a new novnc release 0.5.1 > however this still does not fix all of the outstanding bugs regarding special > characters (afaik). I didn't test it myself, though. Per github ticket it's not likely getting fixed fully any time soon. Can you confirm 0.5.1 helps at least with some of the issues?
this low prio bug didn't make it for 3.6 beta cutoff, moving to 4.0
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
There is no reasonable solution available upstream, not even a plan. There were some improvements in 0.5.1 but it seems that's all novnc can do in foreseeable future