Bug 2064602

(In reply to Guo, Zhiyi from comment #0)
> Description of problem:
> qemu-kvm has supported copy/paste in the vnc console since qemu-kvm 6.2.0,
> see:
> Bug 1874926 - [RFE] copy/paste support in qemu VNC console
> 
> Beside Libvirt, virt-viewer should also support this feature.
> 
> 
> Steps to Reproduce:
> 1.Start VM with VNC has copy/paste enabled, use virt-viewer connect to VM
> vnc port
> 2.Try to copy some characters from client machine and paste them to VM
> 3.Try to copy some characters from VM and paste them to client machine
> 
> Actual results:
> copy/paste in step 2 and 3 doesn't work
> 
> Expected results:
> copy/paste works good
> 
> Additional info:
> I have checked virt-viewer-11.0-1.el9.x86_64 and copy/paste doesn't work. As
> a reference, vncviewer provided by tigervnc-1.11.0-21.el9.x86_64 has
> copy/paste works

I've only done a cursory investigation so far, but I suspect that there may need to be some work done in gtk-vnc as well. One potentially significant difference between vncviewer/tigervnc and virt-viewer is that vncviewer sends a SetEncodings[1] message to the server when it connects, and this message includes the pseudo-encoding value 0xc0a1e5ce[2], which causes qemu to enable some clipboard-related functionality. 

[1] https://datatracker.ietf.org/doc/html/rfc6143#section-7.5.2
[2] https://gitlab.com/qemu-project/qemu/-/blob/1d60bb4b14601e38ed17384277aa4c30c57925d3/ui/vnc.h#L425

(In reply to Jonathon Jongsma from comment #2)
> I've only done a cursory investigation so far, but I suspect that there may
> need to be some work done in gtk-vnc as well. One potentially significant
> difference between vncviewer/tigervnc and virt-viewer is that vncviewer
> sends a SetEncodings[1] message to the server when it connects, and this
> message includes the pseudo-encoding value 0xc0a1e5ce[2], which causes qemu
> to enable some clipboard-related functionality. 

That is the extended clipboard protocol:

  https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#extended-clipboard-pseudo-encoding

GTK-VNC does not implemenet that extension at this time. It only supports the original crude clipboard protocol 

  https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#clientcuttext
  https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#servercuttext

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days