+++ This bug was initially created as a clone of Bug #1477171 +++
SPICE protocol supports copy-paste for different types of data between client and guest. This mechanism is broken when users tries to copy an image from Windows10 Guest and Paste it to Client.
Guest: Windows 10
spice-qxl-wddm-dod-0.18-1
vdagent-win-4.1-3
How reproducible: always
Steps to Reproduce:
1. Log in to Admin or User portal.
2. Have a running Windows 10 VM.
3. Connect to remote desktop of the VM.
4. In the Windows10 open a paint program.
5. Copy an image from paint.
6. Try to paste image at client.
Actual results: cannot-copy paste image data from guest to client.
Additional info: This bug doesn't depend on client.
--- Additional comment from Victor Toso on 2017-08-01 08:41:54 EDT ---
Could you please attach the logs from vdagent-win and the client?
--- Additional comment from Victor Toso on 2017-08-01 08:48:28 EDT ---
Also, could you please double check if this also happens on windows 7?
--- Additional comment from Uri Lublin on 2017-08-01 09:02:06 EDT ---
The image (bmp/png) copy/paste failure is a known issue with the
mingw build and has already been fixed upstream.
To be fixed on the next build.
--- Additional comment from Andrei Stepanov on 2017-08-01 10:25:42 EDT ---
Copy-paste image bug from Guest->Client has place only for Windows10 guest. Windows7 guest doesn't have such bug.
--- Additional comment from Victor Toso on 2017-08-01 10:39:09 EDT ---
Considering comment #3
--- Additional comment from Uri Lublin on 2017-08-01 11:04:55 EDT ---
(Adding to comment #3 and comment #5)
https://lists.freedesktop.org/archives/spice-devel/2017-July/038946.html
I cannot reproduce this bug with a new vdagent-win-4.1-5.
Checked with: Windows7 32bit client and Windows 7 64bit, Windows 10 32bit guests.
Move to VERIFIED.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2017:2746