Hi Antoine,
> However, but there's still a more serious problem, which is also pretty
> weird. If I do:
[..]
> because I can still work around the grab using multiple fingers (i.e.,
> press somewhere, then interact with chromium). This is exactly like
> the bug I reported in the original xtrlock, with the only difference
> that the mouse pointer does not move while I do it.
I can partly reproduce this, as well as some other strange behaviour
upon "plugging in" a device that, like your descriptions, are quite involved
to explain!
> So the regrab doesn't actually solve things. What is even weirder is
> that this problem with the screen not being "correctly" grabbed will
> persist on future xtrlock runs
[…]
> Can you reproduce this pretty weird behavior? Does it make any sense to
> you?
I did once actually but I think I dismissed it as some kind of weird
errant process or just an issue as I was doing lot of recompilation,
etc. etc. Hmpf.
> [The exact same behavior seems to occur if I replace xinput
> enable/disable with the corresponding play with the authorized file.]
I am pleased that we can also get the same behaviour using xinput vs
"authorized" as I would have more confidence that the latter emulates
Eve plugging in a external USB device versus xinput in terms of
abstraction layers.
I'm a little stuck on how to proceed code-wise so my next steps are to
contact the maintainers of the Input Extension and see if they have
any insight.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org 🍥 chris-lamb.co.uk
`-
