Grab keyboard on wayland/gnome3

[yarlz]

I'm using VMWare Workstation Player 15.5.2 build-15785246 on arch linux, running gnome3 + GDM (so wayland, not xorg). My guest OS is Windows 10.

The player fails to capture my keyboard, which is rather annoying since I can't use the windows shortcuts (i.e. Win+E for explorer, Windows key for start menu).

I have tried whitelisting the app, by running

gsettings set org.gnome.mutter.wayland xwayland-allow-grabs true

gsettings set org.gnome.mutter.wayland xwayland-grab-access-rules "['Vmplayer']"

This didn't work though. It does do the trick for Virtualbox. Perhaps a look at their source can help.

[RDPetruska]

Do you have the VMware Tools installed?

[yarlz]

on my guest system? yes.

[yarlz]

I'd like to add that pressing win+E results while vmware is supposedly grabbing my keyboard, triggers the gnome action i configured for that key.

[xrishox]

I'm having the same issue with fedora 32 running gnome 3 and wayland. I hope you guys work toward supporting wayland natively.

[cmprmsd]

For me, the current state under Wayland is, how it should be.

In Virtualbox you can configure, if you want to pass hotkeys to the VM or have them active on the host.

I really appreciate having hotkeys, that do always work e.g. switch workspaces on the host with my hotkeys and have other hotkeys for the VMs.

If VMware is planning to change this, they should make it configurable.
I would also like to have this option within X11 and i3, but up to now, nothing has changed in this aspect.

[tom___]

> the current state under Wayland is, how it should be

What do you mean? This problem still exists for me even under workstation 16.

Has anyone figured out a way to get workstation to properly route all keys to a guest on wayland? I know it works on Xorg, but VMWare claims support for wayland, and I would argue this problem makes workstation unusable.

[toomuchgottscha]

im wondering why the input grab works with virtualbox. there must be some kind of list for applications that allow this under wayland.

[xrishox]

i would like to see this issue fixed as well

[DacianMarin]

I would like to see this issue fixed as well

[dlech]

This looks like the VirtualBox patch for how they fixed it: https://www.virtualbox.org/ticket/19650

Workarounds for a few things:

• WIN+ALT+TAB instead of ALT+TAB
• CTRL+ESC to open start menu

[stuckj2]

For now just adding Super to your shortcut seems to be the only viable workaround (e.g., Super-Alt-Tab instead of Alt-Tab, etc). Not ideal, but better than having no shortcut.

Definitely interested in a fix from vmware on this.

[banackm]

The vmplayer binary just runs the UI, not the console.

Try adding exceptions for the vmware-vmx and mksSandbox binaries instead?

[stuckj2]

Thanks @banackm. I tried this, but still no luck:

gsettings get org.gnome.mutter.wayland xwayland-allow-grabs "true"
gsettings set org.gnome.mutter.wayland xwayland-grab-access-rules "['vmplayer','vmware-vmx','mksSandbox']"

I would think it is the UI that needs the grab exception, right? Since that is the part interacting with mutter.

[banackm]

The actual VM console window isn't rendered by the UI process on Linux, no.

Can you post the vmware.log and mksSandbox.log from your setup?

[stuckj2]

Sure. I'm attaching them to this reply from a resume I just did.