https://bugs.freedesktop.org/show_bug.cgi?id=107358
--- Comment #7 from mikhail.v.gavri...@gmail.com ---
(In reply to Olivier Fourdan from comment #6)
> To demonstrate that, I attached a very simple reproducer written in gtk2.
>
> If you compile and run that reproducer on Wayland/Xwayland, it will bejave
> the same, no other X11 client wil lreceive pointer events as long as the
> client is running, whereas other Wayland native clients will remain
> unaffected.
>
> In other words, this is normal.
You even overdid it, the game did not block the keyboard.
But I admit you were able to recreate the same effect.
I do not understand why you think this behavior is normal.
In a multitasking environment, when one application can influence another it is
perceived as a system vulnerability.
It also opens up a large field of activity of extortionists software and simply
poorly written software, which will create the illusion that the computer is
frozen.
When I studing several year ago Wayland architecture I thought that for each
X11 application would used separate XWayland client this allow fix all XServer
problems in modern systems. At that time it was a problem with Remmina which
sometimes did not want to give away control of mouse and keyboard and I had to
kill XServer every time through the console.
I think this should be fixed in Wayland environment for all type of
applications.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
