On Thu, 2017-09-07 at 10:28 +0100, Frediano Ziglio wrote:
> You could easily trigger this issue using multiple monitors and a
> modified spice-gtk client with this patch:
>
> --- a/src/channel-main.c
> +++ b/src/channel-main.c
> @@ -1699,6 +1699,7 @@ static gboolean _channel_new(channel_new_
You could easily trigger this issue using multiple monitors and a
modified spice-gtk client with this patch:
--- a/src/channel-main.c
+++ b/src/channel-main.c
@@ -1699,6 +1699,7 @@ static gboolean _channel_new(channel_new_t *c)
{
g_return_val_if_fail(c != NULL, FALSE);
+if (
> On 30 Aug 2017, at 10:53, Frediano Ziglio wrote:
>
>>
>>> On 30 Aug 2017, at 10:19, Frediano Ziglio wrote:
>>>
>>> You could easily trigger this issue using multiple monitors and
>>> a modified client with this patch:
>>>
>>> --- a/src/channel-main.c
>>> +++ b/src/channel-main.c
>>> @@ -16
>
> > On 30 Aug 2017, at 10:19, Frediano Ziglio wrote:
> >
> > You could easily trigger this issue using multiple monitors and
> > a modified client with this patch:
> >
> > --- a/src/channel-main.c
> > +++ b/src/channel-main.c
> > @@ -1699,6 +1699,7 @@ static gboolean _channel_new(channel_new_
> On 30 Aug 2017, at 10:19, Frediano Ziglio wrote:
>
> You could easily trigger this issue using multiple monitors and
> a modified client with this patch:
>
> --- a/src/channel-main.c
> +++ b/src/channel-main.c
> @@ -1699,6 +1699,7 @@ static gboolean _channel_new(channel_new_t *c)
> {
> g_
You could easily trigger this issue using multiple monitors and
a modified client with this patch:
--- a/src/channel-main.c
+++ b/src/channel-main.c
@@ -1699,6 +1699,7 @@ static gboolean _channel_new(channel_new_t *c)
{
g_return_val_if_fail(c != NULL, FALSE);
+if (c->type == SPICE_CHANN
