On Sat, Jul 29, 2017 at 11:17 AM, Mart Raudsepp <[email protected]> wrote:
> Ühel kenal päeval, L, 29.07.2017 kell 13:20, kirjutas [email protected]:
>> The task is already accomplished :) with a mixture of WM-based
>> hotkey definitions and a delayed commandline utility (main,scrot,
>> imagemagick).
>> Addtionally I dont think that my X11 uses framebuffer (not shure
>> about that, though)...
>
> Those tools work by using an inherent X11 security hole by reading out
> the root window, it's not relevant to framebuffer in the kernel sense.
>
> Note that you can't use a global shortcut key in X11 while a typical
> right click context menu is open, because these take a X11 grab and
> even screen lock can't activate.. Then only the delay approach will
> work (if desired then together with a shortcut if the shortcut key is
> hit before opening the context menu). Fortunately in this case you only
> wanted a dropdown in firefox, which isn't implemented like that.
> This popup menu problem is solved with Wayland (most importantly the
> not screenlocking aspect of it), but so is the root window security
> hole, so the compositor/WM needs to take the screenshot and tools like
> import/scrot won't work.
>

I'm not really sure it is fair to call that a security problem. It's
intentional, and that is because there are plenty of things that need
access to the whole desktop at once. E.g. automating anything that
doesn't expose a development API or have an accessibility API can
pretty much only be done by scraping the contents of the screen -
these programs simply don't work in Wayland? That seems like a
misfeature.

R0b0t1.

Reply via email to