Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1169679

Summary: Multiple keys added on keystroke in guest console VNC connection via remote-viewer
Product: Red Hat Enterprise Linux 7 Reporter: Lukas Svaty <lsvaty>
Component: gtk-vncAssignee: Daniel Berrangé <berrange>
Status: CLOSED WORKSFORME QA Contact: Desktop QE <desktop-qa-list>
Severity: urgent Docs Contact:
Priority: medium    
Version: 7.0CC: cfergeau, danken, hannsj_uhl, ipinto, istein, kgoldbla, lpeer, lsurette, lsvaty, mavital, michal.skrivanek, Rhev-m-bugs, rmm, srevivo, tpelka
Target Milestone: pre-dev-freezeKeywords: Reopened
Target Release: 7.5   
Hardware: ppc64   
OS: Linux   
Whiteboard: virt
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-17 14:25:52 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:
Bug Depends On:    
Bug Blocks: 1122979, 1444027    

Description Lukas Svaty 2014-12-02 07:57:38 UTC 
Description of problem:
When trying to connect to VM via VNC on RHEV for IBM host. On key stroke multiple charracters are created in console.

Version-Release number of selected component (if applicable):
quest kernel-2.6.32-431.el6.ppc64
used virt-viewer-0.6.0-1.fc20.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Add VM
2. Run VNC
3. Try to create some sensible text

Actual results:
Most charracters are replicated numerous time after stroking key on keyboard for more than fraction of a second.

Expected results:
Delay on character repeat when key is held down.

Additional info:
Nothing suspicious is in vdsm/engine.log. If any logs neccessary please put needinfo specifying which ones on me and I can attach.
Comment 1 Dan Kenigsberg 2014-12-02 12:55:49 UTC 
Does vnc work properly when oVirt is not involved?

Could you fire a ppc64 qemu process from the command line, and connect to it with your vnc client?

Which qemu version is this?
Comment 2 Michal Skrivanek 2014-12-02 13:57:16 UTC 
this does not sound related. Might be a general issue on VNC server or client side. I would guess you reproduce it without oVirt involvement as well (you can use kimchi to manage VMs on stock PowerKVM)
Comment 3 Lukas Svaty 2014-12-04 10:05:20 UTC 
I was unable to reproduce it in qemu, but nor in ovirt. With the same quest, or guest without OS. Any idea what might be the problem?
Kevin is it still reproducible for you?
Comment 4 Kevin Alon Goldblatt 2014-12-07 20:45:54 UTC 
Adding this info for again. Yes this happens all the time on the PPC FC system. Every keystroke is repeated at least 2 or more times vi the VNC. Even log in takes quite a while.

In addition to the keystroke issue the VNC display is so dark that one can barely make out the text
Comment 5 Kevin Alon Goldblatt 2014-12-08 08:37:10 UTC 
Yes this happens every time I access the guest via KVM. Every key stroke is displayed 2 or more time. Even logging in can take a while 

The other problem is the kvm screen which is so dark, one can hardly make out the text ouput...
Comment 6 Michal Skrivanek 2014-12-08 10:33:38 UTC 
(In reply to Kevin Alon Goldblatt from comment #5)
> Yes this happens every time I access the guest via KVM. Every key stroke is
> displayed 2 or more time. Even logging in can take a while 

since it's not reproducible for others I'd suspect client's issue.

did you try comment #1/#2 ?
Comment 7 Michal Skrivanek 2014-12-08 10:34:36 UTC 
(In reply to Kevin Alon Goldblatt from comment #5)
> The other problem is the kvm screen which is so dark, one can hardly make
> out the text ouput...

unrelated. bug 1142733
Comment 8 Kevin Alon Goldblatt 2014-12-17 13:50:41 UTC 
(In reply to Dan Kenigsberg from comment #1)
> Does vnc work properly when oVirt is not involved?
> 
> Could you fire a ppc64 qemu process from the command line, and connect to it
> with your vnc client?
> 
> Which qemu version is this?

Dan can you provide a description of how I must "fire a ppc64 qemu process from the command line, and connect to it
> with your vnc client".
Comment 9 Dan Kenigsberg 2014-12-17 20:47:09 UTC 
to your question:

    qemu-kvm -vnc :0

should start listening on the local port 5900. But if the issue no longer reproduces via oVirt/RHEV, there's no much point attempting to reproduce it directly.
Comment 10 Michal Skrivanek 2014-12-23 09:22:35 UTC 
any luck (not) reproducing without ovirt involvement, using the same client?
Comment 11 Michal Skrivanek 2015-01-08 13:57:22 UTC 
any news?
Comment 14 Michal Skrivanek 2015-01-16 11:15:59 UTC 
not sure what you're doing...
tried on the first host with vncviewer(tigervnc), works fine.
tried qemu-kvm directly, works fine
Comment 15 Lukas Svaty 2015-12-18 13:17:19 UTC 
Issue re-appeared while testing 3.6. Can provide reproduction environment.
Comment 16 Lukas Svaty 2015-12-18 13:17:25 UTC 
*** Bug 1292784 has been marked as a duplicate of this bug. ***
Comment 17 Ilanit Stein 2015-12-27 09:56:15 UTC 
This issue occur also on the rhel 7.2 guest spice console,
on various rhevm envs, with different ppc hosts.
(managed to login via spice after several trials, as the letters typed are duplicated) 

Versions:

- ppc host:

OS Version: RHEL - 7.2 - 9.el7
Kernel Version: 3.10.0 - 327.2.1.el7.ppc64le
KVM Version: 2.3.0 - 31.el7_2.4
LIBVIRT Version: libvirt-1.2.17-13.el7_2.2
VDSM Version: vdsm-4.17.13-1.el7ev

- guest:
Kernel Version: 3.10.0 - 327.2.1.el7.ppc64le
Comment 18 Ilanit Stein 2016-01-06 15:59:59 UTC 
Correction to comment 17:
Display was VNC and not SPICE.
Connection was of VNC via remote-viewer.

If using tigervnc, instead of remote-viewer, the problem of duplicated letter do not exist,

so problem seem to be with remote-viewer specifically.

This problem happen only on PPC environment.

All these guests were tested with remote-viewer, and show this problem:
RHEL-7.2-Server-ppc64le kernel 3.10.0-327.2.1.el7.ppc64le
RHEL-7.1-20150219.1-Server-ppc64 kernel 3.10.0-229.el7.ppc64
RHEL-6.7-20150429.0-Server-ppc64 kernel 2.6.32-554.el6.ppc64
RHEL-LE-7.1-20150219.1-Server-ppc64le kernel 3.10.0-229.ae17b.ppc64le
Comment 19 Christophe Fergeau 2016-01-06 16:08:10 UTC 
Tentatively moving to gtk-vnc (could be virt-viewer too).
Comment 21 Daniel Berrangé 2017-04-12 11:01:57 UTC 
Can you run 'remote-viewer' with the --gtk-vnc-debug flag set and reproduce the duplicate key strokes problem. Then attach the complete resulting log to this bug.
Comment 22 Daniel Berrangé 2017-04-12 11:02:56 UTC 
Also please confirm what platform you're running remote-viewer  on ? Is it also on the same ppc host as the VM, or is it on a separate remote x86 host
Comment 23 Lukas Svaty 2017-04-25 06:51:07 UTC 
moving needinfo to Ilanit, as I do not have resources to this anymore
Comment 24 Ilanit Stein 2017-04-25 07:19:11 UTC 
Moving to RHV/Virt QE team manager, as I no longer work in this team.
Comment 25 meital avital 2017-06-21 07:35:57 UTC 
Israel, please provide the needed info
Comment 26 Israel Pinto 2017-06-28 06:43:54 UTC 
Hi all, (i don't know if it still relevant)
I check it with  remote-viewer --gtk-vnc-debug, see output below.
The console is open with no error, also without --gtk-vnc-debug it opened.
Output:
ipinto@dhcp-4-168 ~/Downloads ❯❯❯ remote-viewer --gtk-vnc-debug console.vv                                                                                                     (9:41)
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Init VncConnection=0x564a9ea0dba0
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplaykeymap.c Using Wayland evdev virtual keycode mapping
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now Control_L+Alt_L
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Open host=10.16.69.168 port=5900
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Open coroutine starting
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Started background coroutine
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Resolving host 10.16.69.168 5900
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Trying one socket
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Socket pending
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Finally connected
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 13
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Grab sequence is now 
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Connected to VNC server
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Protocol initialization
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable

(remote-viewer:7628): Gtk-WARNING **: Allocating size to VncDisplay 0x564a9ea08250 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached

(remote-viewer:7628): libgovirt-CRITICAL **: file ovirt-utils.c: line 152 (ovirt_utils_genum_get_value): should not be reached
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Server version: 3.8
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Sending full greeting
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Using version: 3.8
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Possible auth 2
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 11
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Thinking about auth type 2
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Decided on auth type 2
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Waiting for auth type
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Choose auth 2
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Do Challenge
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting missing credentials
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 10
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Set credential 0 qsgFDsM9ynnZ
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Waiting for missing credentials
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Got all credentials
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Checking auth result
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Success
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Initial desktop size 1024x768
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Pixel format BPP: 32,  Depth: 24, Byte order: 1234, True color: 1
             Mask  red: 255, green: 255, blue: 255
             Shift red:  16, green:   8, blue:   0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Display name 'QEMU (golden_env_mixed_virtio_2_2)'
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 14
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Using default colour depth 24 (32 bpp) (true color? 1)
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Set depth color to 24 (32 bpp)
(remote-viewer:7628): gtk-vnc-DEBUG: vnccairoframebuffer.c Surface 1024x768
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Set framebuffer 0x564a9f5cf8d0
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Removed encoding -27
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Sending 13 encodings
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Requesting first framebuffer update
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 0
(remote-viewer:7628): gtk-vnc-DEBUG: vncdisplay.c Initialized VNC server
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Running main loop
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-259 area (1024x768) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Audio encoding support
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-258 area (1024x768) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Keyboard mode extended
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Re-requesting framebuffer update at 0,0 size 1024x768, incremental 0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=-257 area (1024x768) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Pointer mode relative
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Re-requesting framebuffer update at 0,0 size 1024x768, incremental 0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (1024x18) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncbaseframebuffer.c Mask local: 255 255 255
    remote: 255 255 255
    merged: 255 255 255
(remote-viewer:7628): gtk-vnc-DEBUG: vncbaseframebuffer.c Pixel shifts
   right:  16   8   0
    left:  16   8   0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (1024x18) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (343x29) at location 0,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (343x29) at location 0,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (343x19) at location 0,47
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (343x19) at location 0,47
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (133x13) at location 0,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (133x13) at location 0,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (133x689) at location 0,79
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (133x689) at location 0,79
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (210x702) at location 133,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (210x702) at location 133,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (681x750) at location 343,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (681x750) at location 343,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (1024x18) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (1024x18) at location 0,0
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (343x29) at location 0,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (343x29) at location 0,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (343x19) at location 0,47
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (343x19) at location 0,47
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (133x13) at location 0,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (133x13) at location 0,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (133x689) at location 0,79
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (133x689) at location 0,79
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (210x702) at location 133,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (210x702) at location 133,66
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c FramebufferUpdate type=7 area (681x750) at location 343,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Notify update area (681x750) at location 343,18
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Emit main context 4
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Requesting framebuffer update at 0,0 size 1024x768, incremental 1
(remote-viewer:7628): gtk-vnc-DEBUG: vncconnection.c Read error Resource temporarily unavailable
Comment 27 Israel Pinto 2017-06-28 06:46:09 UTC 
Adding rhevm and host versions
Engine: Red Hat Virtualization Manager Version: 4.1.3.5-0.1.el7
Host: 
OS Version:RHEL - 7.4 - 17.el7
Kernel Version: 3.10.0 - 514.26.1.el7.ppc64le
KVM Version: 2.9.0 - 14.el7
LIBVIRT Version: libvirt-3.2.0-14.el7
VDSM Version: vdsm-4.19.20-1.el7ev
Comment 28 Daniel Berrangé 2018-08-17 14:25:52 UTC 
Closing as there's no sign of any bug in the logs, I can't reproduce it anywhere, and its highly unlikely that there would be an architecture specific bug in this client side code regardless.