One main difference between x11 and wayland is that in x11 all applications receive all input whereas in wayland the compositor receives input and decides which application may receive it. This causes a major issue with application which need to grab keyboard input for running or showing a nested desktop. This affects e.g. GUI virtual machines (SPICE clients), RDP clients, VNC clients, nested kwin/gnome-shell/whatever. Without giving these wayland clients the ability to grab input, they will not be able to handle keys which are also global key bindings in your wayland compositor, e.g. Alt+Tab or the Super key. Games might also be affected, I don't know that for sure. I'm posting this here to raise attention because 1. to fix this we need another protocol (extension) 2. this issue can't be fixed in a single application, it needs the whole stack (wayland library, compositors, affected applications) to change IMHO, this is the biggest important feature that's still missing for wayland to be ready for production. See also: https://bugzilla.redhat.com/show_bug.cgi?id=1285770 https://lists.fedoraproject.org/archives/list/desktop@lists.fedoraproject.org/thread/BBPOOC4GVBJXHLKSSFLGERG6GYAU6M6U/
This is a major issue for users of assistive technology who rely on the keyboard to navigate within virtual machines. Critical key bindings such as Alt+Tab, the Super key and so on are not supported.
Yes. Please use the X11 session in such cases until this is fixed.
+1 ... having issues sending win alt-tab and other keys to VirtualBox, FreeRDP, vncviewer etc.
Virtual Desktops makes it easy to switch hardware and take backups. Businesses often have Windows Terminal Servers for their applications. Wayland preventing Alt+Tab and Alt+F4 inside VirtualBox VMs and Remmina connections makes Wayland unusable for the regular office users I manage. It will be really nice when Wayland is usable for this purpose.
Looks like this bug can be closed? https://lists.freedesktop.org/archives/wayland-devel/2017-July/034459.html
*** Bug 104051 has been marked as a duplicate of this bug. ***
(In reply to ringe from comment #5) > Looks like this bug can be closed? > https://lists.freedesktop.org/archives/wayland-devel/2017-July/034459.html Yes, I believe the issue is solved for Wayland. What is remaining is independent feature requests for each compositor and related application to make use of the extension if they do not already.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.