Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Java VNC viewer is not able to accept clipboard data from QEMU VNC Server #1855

Open
yanjiew1 opened this issue Oct 21, 2024 · 1 comment
Open
Assignees

Comments

@yanjiew1
Copy link

Describe the bug
It is not possible to copy text in the guest OS and paste the text in the host OS when using the Java VNC viewer of TigerVNC to connect to the QEMU VNC Server. However, the native VNC viewer of TigerVNC works.

The host OS is Fedora 40.
The QEMU version is 8.2.7.
The guest OS is Windows 10 with spice-vdagent installed.
The qemu-vdagent channel is created for the guest to send the clipboard data.

To Reproduce
Steps to reproduce the behavior:

  1. Create a VM using virt-manager. Use VNC as display, and configure qemu-vdagent channel for clipboard sharing.
  2. Install Windows 10 in the VM.
  3. Install spice-vdagent in the VM.
  4. Use Java VNC viewer to connect to the guest, and try to copy some text in the guest, and then try to paste the text in the host OS. The text cannot be pasted.

Expected behavior
After copying the text in the guest, the text can be pasted in host OS.

Screenshots
If applicable, add screenshots to help explain your problem.

Client (please complete the following information):

Server (please complete the following information):

  • OS: Fedora KDE Plasma Desktop
  • VNC server: QEMU
  • VNC server version: 8.2.7
  • Server downloaded from: QEMU from Fedora 40's official repository.
  • Server was started using: The VM is started by libvirtd, and the server is built in the QEMU.

Additional context
The Java VNC viewer of TurboVNC also does not work, and the error message shown in TurboVNC is "ZlibInStream: inflate failed". I suspects that the problem is in the jzlib library because the native version of TigerVNC viewer works correctly.

@CendioOssman
Copy link
Member

Thanks for your report.

Have you also reported the issue to TurboVNC? It would probably be good to link the issues in that case, so we can share any findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants