>
> Hi,
>
> On Thu, Dec 15, 2016 at 12:10:46PM -0500, Frediano Ziglio wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Dec 14, 2016 at 05:07:17PM -0500, Frediano Ziglio wrote:
> > > > >
> > > > > Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
> > > > > Lock/Unlock events from Sess
Hi,
On Thu, Dec 15, 2016 at 12:10:46PM -0500, Frediano Ziglio wrote:
> >
> > Hi,
> >
> > On Wed, Dec 14, 2016 at 05:07:17PM -0500, Frediano Ziglio wrote:
> > > >
> > > > Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
> > > > Lock/Unlock events from Session at VDAgent. That se
>
> Hi,
>
> On Wed, Dec 14, 2016 at 05:07:17PM -0500, Frediano Ziglio wrote:
> > >
> > > Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
> > > Lock/Unlock events from Session at VDAgent. That seemed to work fine
> > > but as pointed by Andrei at [0], it does not cover the follo
Hi,
On Wed, Dec 14, 2016 at 05:07:17PM -0500, Frediano Ziglio wrote:
> >
> > Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
> > Lock/Unlock events from Session at VDAgent. That seemed to work fine
> > but as pointed by Andrei at [0], it does not cover the following
> > situatio
>
> Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
> Lock/Unlock events from Session at VDAgent. That seemed to work fine
> but as pointed by Andrei at [0], it does not cover the following
> situation:
>
> > It fails for next test-case:
> >
> > * Connect with RV to VM
> > * Loc
Commit 5907b6cbb5c724f9729da59a644271b4258d122e started to handle
Lock/Unlock events from Session at VDAgent. That seemed to work fine
but as pointed by Andrei at [0], it does not cover the following
situation:
> It fails for next test-case:
>
> * Connect with RV to VM
> * Lock VM (ctrl-alt-del)
>
