Hi,
> I fail to see how that works, imagine the other end is the same code (qemu
> in the guest), it will take clipboard ownership and it is in a endless
> loop, isn't it?
Notifications on guest-triggered clipboard updates will not be sent back
to the guest, exactly to avoid that kind of loop. See self_update
checks in vdagent_clipboard_notify(). gtk and vnc notify callbacks have
simliar checks for simliar reasons ;)
That means the other side may have wrong clipboard expectations. It may ask for what was previously an image and that will fails. This is not a big issue per se if error returns are handled correctly all the way. It may also have an impact on some UI aspects (since some actions shold become unactive when clipboard has some content or another etc)