Hey,
On Wed, May 09, 2018 at 01:20:19PM +0200, Lukáš Hrázký wrote:
> On Wed, 2018-05-09 at 05:18 -0400, Frediano Ziglio wrote:
> > The agent send a single message, but reads/writes to the device are
> > not atomic. Note that the current protocol introduce additional
> > delays as the frames cannot
On Tue, 2018-06-12 at 13:30 +0200, Christophe Fergeau wrote:
> Hey,
>
> On Wed, May 09, 2018 at 01:20:19PM +0200, Lukáš Hrázký wrote:
> > On Wed, 2018-05-09 at 05:18 -0400, Frediano Ziglio wrote:
> > > The agent send a single message, but reads/writes to the device are
> > > not atomic. Note that
Hi,
On Fri, Jun 08, 2018 at 04:25:29PM +0200, Christophe Fergeau wrote:
> Signed-off-by: Christophe Fergeau
> ---
> NEWS | 23 +++
> configure.ac | 2 +-
> spice-common | 2 +-
> 3 files changed, 25 insertions(+), 2 deletions(-)
>
> diff --git a/NEWS b/NEWS
> index
SPICE expect to have each frame in a single message.
So far the stream-device did not do that.
That works fine for H264 streams but not for mjpeg.
The client handles by itself mjpeg streams, and not via
gstreamer, and is assuming that a message contains the
whole frame. Since it currently not, usin
This patch is potentially problematic.
As I understand, this will prevent us from trying to configure the
monitors until we receive the monitor config from the server.
This can conflict with our 'fullscreen' mode in virt-viewer. In this
mode, we start up and immediately (as soon as the vdagent is
