[Spice-devel] [spice-gtk v2] gtk-session: clipboard request: notify agent on failure

[james harvey]

On Wed, Jan 16, 2019 at 6:08 AM Marc-André Lureau
<marcandre.lureau at gmail.com> wrote:
> On Wed, Jan 16, 2019 at 2:47 PM james harvey <jamespharvey20 at gmail.com> wrote:
> > Am I understanding correctly that the Jan 10 patches which completely
> > fix spice for me and others experiencing clipboard problems aren't
> > being added in any form, and that instead the clipboard is being left
> > broken, just less broken so it doesn't freeze the guest?  I don't know
> > exactly when it broke, but spice didn't used to act this way.
>
> That's important information, because spice-gtk clipboard code didn't
> change that much afaik.

I can definitely understand when it broke would be helpful.
Unfortunately, there is a couple of years gap in my spice usage, so I
don't think it's something I can pin down.  I don't know if it would
be possible to run years old spice, or if dependencies from or to
spice would get tripped up and spin the project into basically
bisecting an entire system as a whole, based on packages available on
given dates.  Even if it was, it's of course possible it might be
another package's change that made this stop working.  While that
would be possible to do given Arch's historical repos, it would be a
massive undertaking.  With the amount of other project bisecting I've
done lately, it's not something I'd be able to do anytime soon.

> > That's going to leave me and others perpetually patching spice
> > releases, and someday when they don't apply cleanly, being at a loss
> > and being forced to look at other protocols.
> >
> > Apologies if I'm misunderstanding.
>
> You misunderstand, there is a lot of activity on this problem atm and
> it is currently scheduled for 0.36. However, since it is not clear
> whether this is a regression and the fixes are *not* trivial, it
> should be fine to schedule for 0.37. Either early release after that,
> and fixes can be backported too most probably.

Glad to hear!