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.
Description of problem:
Wrongly recognize input '|' to '>' in qemu guest via vnc
Version-Release number of selected component (if applicable):
tigervnc-icons-1.8.0-4.el7.noarch
gvnc-0.7.0-2.el7.x86_64
tigervnc-license-1.8.0-4.el7.noarch
gtk-vnc2-0.7.0-2.el7.x86_64
gtk-vnc-debuginfo-0.7.0-2.el7.x86_64
tigervnc-1.8.0-4.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. In one terminal on the host, boot a guest via qemu with '-vnc :0'
(qemu) info vnc
default:
Server: :::5900 (ipv6)
Auth: none (Sub: none)
Server: 0.0.0.0:5900 (ipv4)
Auth: none (Sub: none)
Client: ::1:38890 (ipv6)
x509_dname: none
sasl_username: none
2. In another terminal on the same host, start vncviewer
# vncviewer :0
TigerVNC Viewer 64-bit v1.8.0
Built on: 2017-10-27 05:09
Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Sun Jan 14 20:18:43 2018
DecodeManager: Detected 24 CPU core(s)
DecodeManager: Creating 4 decoder thread(s)
CConn: connected to host localhost port 5900
CConnection: Server supports RFB protocol version 3.8
CConnection: Using RFB protocol version 3.8
CConnection: Choosing security type None(1)
Sun Jan 14 20:18:44 2018
CConn: Using pixel format depth 24 (32bpp) little-endian rgb888
CConn: Using Tight encoding
3. in the guest, in the vnc window -> open a terminal -> input '|'(shift+\) or '<'(shift+,), they will be recognized as '>'.
Actual results:
in the guest, in the vnc window -> open a terminal -> input '|'(shift+\) or '<'(shift+,), they will be recognized as '>'.
Expected results:
input '|'(shift+\) --> show '|'
input '<'(shift+,) --> show '<'
Additional info:
1. works well via ssh to login guest
2. same problem via remote-viewer
3. qemu CML:
/usr/libexec/qemu-kvm \
-S \
-name 'avocado-vt-vm1' \
-sandbox off \
-machine q35 \
-nodefaults \
-vga cirrus \
-device i82801b11-bridge,id=dmi2pci_bridge,bus=pcie.0,addr=0x2 \
-device pci-bridge,id=pci_bridge,bus=dmi2pci_bridge,addr=0x1,chassis_nr=1 \
-device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \
-device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-3,addr=0x0 \
-drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=raw,file=/mnt/rhel75-64-virtio-scsi.raw \
-device scsi-hd,id=image1,drive=drive_image1,serial=12345 \
-device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \
-device virtio-net-pci,mac=9a:19:1a:1b:1c:1d,id=idgMjvea,vectors=4,netdev=idL0Vkvy,bus=pcie.0-root-port-4,addr=0x0 \
-netdev tap,id=idL0Vkvy,vhost=on \
-m 8192 \
-smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \
-cpu 'Opteron_G5',+kvm_pv_unhalt \
-rtc base=utc,clock=host,driftfix=slew \
-boot menu=off,strict=off,order=cdn,once=c \
-enable-kvm \
-monitor stdio \
-vnc :0 \
connect the guest via my laptop which is installed with fc26, same problem:
$ rpm -qa | grep vnc
gvnc-0.7.1-1.fc26.x86_64
tigervnc-icons-1.8.0-1.fc26.noarch
tigervnc-license-1.8.0-1.fc26.noarch
gtk-vnc2-0.7.1-1.fc26.x86_64
tigervnc-1.8.0-1.fc26.x86_64
libvncserver-0.9.11-2.fc26.x86_64
(In reply to Jan Grulich from comment #3)
> Isn't this issue rather in QEMU or libvncserver which QEMU uses internally
> then in tigervnc?
Thanks, it's a qemu bug.
*** This bug has been marked as a duplicate of bug 1513870 ***
Description of problem: Wrongly recognize input '|' to '>' in qemu guest via vnc Version-Release number of selected component (if applicable): tigervnc-icons-1.8.0-4.el7.noarch gvnc-0.7.0-2.el7.x86_64 tigervnc-license-1.8.0-4.el7.noarch gtk-vnc2-0.7.0-2.el7.x86_64 gtk-vnc-debuginfo-0.7.0-2.el7.x86_64 tigervnc-1.8.0-4.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. In one terminal on the host, boot a guest via qemu with '-vnc :0' (qemu) info vnc default: Server: :::5900 (ipv6) Auth: none (Sub: none) Server: 0.0.0.0:5900 (ipv4) Auth: none (Sub: none) Client: ::1:38890 (ipv6) x509_dname: none sasl_username: none 2. In another terminal on the same host, start vncviewer # vncviewer :0 TigerVNC Viewer 64-bit v1.8.0 Built on: 2017-10-27 05:09 Copyright (C) 1999-2017 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. Sun Jan 14 20:18:43 2018 DecodeManager: Detected 24 CPU core(s) DecodeManager: Creating 4 decoder thread(s) CConn: connected to host localhost port 5900 CConnection: Server supports RFB protocol version 3.8 CConnection: Using RFB protocol version 3.8 CConnection: Choosing security type None(1) Sun Jan 14 20:18:44 2018 CConn: Using pixel format depth 24 (32bpp) little-endian rgb888 CConn: Using Tight encoding 3. in the guest, in the vnc window -> open a terminal -> input '|'(shift+\) or '<'(shift+,), they will be recognized as '>'. Actual results: in the guest, in the vnc window -> open a terminal -> input '|'(shift+\) or '<'(shift+,), they will be recognized as '>'. Expected results: input '|'(shift+\) --> show '|' input '<'(shift+,) --> show '<' Additional info: 1. works well via ssh to login guest 2. same problem via remote-viewer 3. qemu CML: /usr/libexec/qemu-kvm \ -S \ -name 'avocado-vt-vm1' \ -sandbox off \ -machine q35 \ -nodefaults \ -vga cirrus \ -device i82801b11-bridge,id=dmi2pci_bridge,bus=pcie.0,addr=0x2 \ -device pci-bridge,id=pci_bridge,bus=dmi2pci_bridge,addr=0x1,chassis_nr=1 \ -device pcie-root-port,id=pcie.0-root-port-3,slot=3,chassis=3,addr=0x3,bus=pcie.0 \ -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pcie.0-root-port-3,addr=0x0 \ -drive id=drive_image1,if=none,snapshot=off,aio=threads,cache=none,format=raw,file=/mnt/rhel75-64-virtio-scsi.raw \ -device scsi-hd,id=image1,drive=drive_image1,serial=12345 \ -device pcie-root-port,id=pcie.0-root-port-4,slot=4,chassis=4,addr=0x4,bus=pcie.0 \ -device virtio-net-pci,mac=9a:19:1a:1b:1c:1d,id=idgMjvea,vectors=4,netdev=idL0Vkvy,bus=pcie.0-root-port-4,addr=0x0 \ -netdev tap,id=idL0Vkvy,vhost=on \ -m 8192 \ -smp 8,maxcpus=8,cores=4,threads=1,sockets=2 \ -cpu 'Opteron_G5',+kvm_pv_unhalt \ -rtc base=utc,clock=host,driftfix=slew \ -boot menu=off,strict=off,order=cdn,once=c \ -enable-kvm \ -monitor stdio \ -vnc :0 \