Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1292784

Summary:	VNC on PPC is unusable due to multiple characters being inserted on single button stroke
Product:	[oVirt] ovirt-guest-agent	Reporter:	Lukas Svaty <lsvaty>
Component:	Core	Assignee:	Vinzenz Feenstra [evilissimo] <vfeenstr>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	---	CC:	bugs
Target Milestone:	---	Flags:	rule-engine: planning_ack? rule-engine: devel_ack? rule-engine: testing_ack?
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-18 13:17:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Lukas Svaty 2015-12-18 10:46:40 UTC

Description of problem:
When using VNC console on PPC host/vm, single stroke of key insert multiple characters to the console, this makes VNC unsusable as user is not able to login.

Version-Release number of selected component (if applicable):
host:
kernel-3.10.0-327.4.1.el7.ppc64le
libvirt-client-1.2.17-13.el7_2.2.ppc64le
qemu-kvm-rhev-2.3.0-31.el7_2.5.ppc64le
vdsm-4.17.13-1.el7ev.noarch

guest:
kernel-3.10.0-327.2.1.el7
rhevm-guest-agent-common-1.0.11-3.el7ev

local:
virt-viewer-2.0-6.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install RHEL VM in on ppc host
2. Download console.vv for VNC start
3. On local machine  run remote-viewer console.vv

Actual results:
Multiple keys inserted on single key press

Expected results:
1:1 ratio

Comment 1 Lukas Svaty 2015-12-18 12:20:03 UTC

Same behaviour appears on noVNC

Comment 2 Lukas Svaty 2015-12-18 13:17:25 UTC

This issue was introduced previously in 3.4 and was fixed there (see BZ#1169679). In 3.6 this issue re-appeared

*** This bug has been marked as a duplicate of bug 1169679 ***