On Wed, Jul 27, 2016 at 03:31:10PM +0200, Fabiano Fidêncio wrote:
> >> diff --git a/src/vmcstream.c b/src/vmcstream.c
> >> index c536f71..32d8b5e 100644
> >> --- a/src/vmcstream.c
> >> +++ b/src/vmcstream.c
> >> @@ -399,9 +399,13 @@ spice_vmc_output_stream_write_finish(GOutputStream
> >> *stream,
On Wed, Jul 27, 2016 at 12:42 PM, Fabiano Fidêncio wrote:
> On Wed, Jul 27, 2016 at 12:39 PM, Christophe Fergeau
> wrote:
>> On Wed, Jul 27, 2016 at 11:17:38AM +0200, Fabiano Fidêncio wrote:
>>> This bogus code was introduced when switching to GTask API. Seems that
>>> while writing those patches
On Wed, Jul 27, 2016 at 12:39 PM, Christophe Fergeau
wrote:
> On Wed, Jul 27, 2016 at 11:17:38AM +0200, Fabiano Fidêncio wrote:
>> This bogus code was introduced when switching to GTask API. Seems that
>> while writing those patches I just overlooked this part and set the wrong
>> result for the t
On Wed, Jul 27, 2016 at 11:17:38AM +0200, Fabiano Fidêncio wrote:
> This bogus code was introduced when switching to GTask API. Seems that
> while writing those patches I just overlooked this part and set the wrong
> result for the task. As part of the problems introduced (and now fixed)
> you can
This bogus code was introduced when switching to GTask API. Seems that
while writing those patches I just overlooked this part and set the wrong
result for the task. As part of the problems introduced (and now fixed)
you can notice that no output stream was being sent to the guest.
Signed-off-by:
