- Mensaje original -
> Hi Marc-Andre,
>
> On 07/18/2012 02:15 PM, Marc-André Lureau wrote:
> > Limit range of monitors, to avoid potential crashes lead by invalid
> > received MonitorConfig values (could be misconfigured or
> > misbehaving
> > guest)
> >
> > This is a a client-side imple
Hi Marc-Andre,
On 07/18/2012 02:15 PM, Marc-André Lureau wrote:
Limit range of monitors, to avoid potential crashes lead by invalid
received MonitorConfig values (could be misconfigured or misbehaving
guest)
This is a a client-side implementation limitation. Eventually, the
range could be inscr
Limit range of monitors, to avoid potential crashes lead by invalid
received MonitorConfig values (could be misconfigured or misbehaving
guest)
This is a a client-side implementation limitation. Eventually, the
range could be inscreased (or unlimited == 0) in the future...
---
gtk/channel-display
On Wed, Jul 18, 2012 at 9:16 AM, Uri Lublin wrote:
> Hi Marc-Andre,
>
>
> On 07/17/2012 08:11 PM, Marc-André Lureau wrote:
>>
>> Limit range of monitors, to avoid potential crashes lead by invalid
>> received MonitorConfig values (could be misconfigured or misbehaving
>> guest)
>>
>> This is a a c
Hi Marc-Andre,
On 07/17/2012 08:11 PM, Marc-André Lureau wrote:
Limit range of monitors, to avoid potential crashes lead by invalid
received MonitorConfig values (could be misconfigured or misbehaving
guest)
This is a a client-side implementation limitation. Eventually, the
range could be inscr
Limit range of monitors, to avoid potential crashes lead by invalid
received MonitorConfig values (could be misconfigured or misbehaving
guest)
This is a a client-side implementation limitation. Eventually, the
range could be inscreased (or unlimited == 0) in the future...
---
gtk/channel-display
