Bug 1116378

Summary:	noVNC does not support crucial keys on some keyboard layouts
Product:	[oVirt] ovirt-engine	Reporter:	Sven Kieske <s.kieske>
Component:	Frontend.WebAdmin	Assignee:	bugs <bugs>
Status:	CLOSED CANTFIX	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs, ecohen, mgoldboi, michal.skrivanek, mlinden, rbalakri, redhat-bugzilla, s.kieske, yeylon
Target Milestone:	ovirt-4.0.0-alpha	Flags:	ylavi: ovirt-4.0.0? ylavi: planning_ack? ylavi: devel_ack? ylavi: testing_ack?
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1566997 (view as bug list)		Environment:
Last Closed:	2015-11-02 10:07:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1566997

Description Sven Kieske 2014-07-04 11:36:14 UTC

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

Comment 1 Michal Skrivanek 2014-08-15 11:00:46 UTC

waiting on next release of noVNC

Comment 2 Sven Kieske 2015-02-20 14:14:10 UTC

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.

Comment 3 Michal Skrivanek 2015-07-30 08:56:02 UTC

(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?

Comment 4 Michal Skrivanek 2015-08-05 12:48:24 UTC

this low prio bug didn't make it for 3.6 beta cutoff, moving to 4.0

Comment 5 Red Hat Bugzilla Rules Engine 2015-10-19 10:49:39 UTC

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.

Comment 7 Michal Skrivanek 2015-11-02 10:07:48 UTC

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