[Spice-devel] Guest clipboard is not available.

[bitozoid]

FTR.

On Mon, Mar 10, 2014 at 1:08 PM, Marc-André Lureau <mlureau at redhat.com> wrote:
>
> ----- Original Message -----
>> On Mon, Mar 10, 2014 at 11:44 AM, Marc-André Lureau <mlureau at redhat.com>
>> wrote:
>> > ----- Original Message -----
>> >> I have a Windows7 guest with KVM/Qemu on a Gentoo host with i3 window
>> >> manager. I have installed all virtio drivers (storage, balloon, serial
>> >> and network) and spice-guest-tools. Vdagent and vdservice are running
>> >> as shown in Windows Task Manager.
>> >>
>> >> However, copy and paste does not work. I have tried with virt-viewer
>> >> and spicy. If I press "Paste to guest" button in spicy I get this
>> >> message:
>> >>
>> >> (spicy:17384): GSpice-WARNING **: Guest clipboard is not available.
>> >>
>> >
>> > spicy is a developer tool, not meant for end users. Please use virt-viewer
>> > instead.
>> >
>> > It's easier for testing if you do Ctrl-C from a text editor in guest (or
>> > client) and try to paste with Ctrl-V in a text editor in client (or
>> > guest).
>> >
>> > While doing this, you can set SPICE_DEBUG=1 environment on client, to
>> > observe the log.
>>
>> I used --debug in virt-viewer. SPICE_DEBUG=1 prints no info. Is there
>> any log file somewhere?
>>
>> SPICE_DEBUG=1 virt-viewer --debug --connect qemu:///system 20140205-win7
>> http://pastebin.com/jygcihfb
>
> Hmm, what version of spice-gtk do you have?
>

spice-gtk-0.21

> try with G_MESSAGES_DEBUG=all SPICE_DEBUG=1 (although that extra env shouldn't be necessary since 0.13)

G_MESSAGES_DEBUG=all SPICE_DEBUG=1 virt-viewer --connect
qemu:///system 20140205-win7
http://pastebin.com/jpUupcGP

>
>>
>> > In Windows, you can also get the vdagent and vdservice logs from
>> > %WINDIR%\temp.
>>
>> vdagent.log
>> http://pastebin.com/Gdxe4B5E
>>
>
> It looks like it doesn't get any clipboard event. Do you have other clipboard tools / managers running on windows?
>

No (afaik).

>> vdservice.log
>> http://pastebin.com/1JuULvHm
>>
>> Both are running as shown in Windows Task Manager.
>>

Thanks a lot anyway.