[Wayland-bugs] [Bug 102475] Can't use keyboard arrows in kvm with the keyboard grabbing change

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Sep 1 07:15:06 UTC 2017


https://bugs.freedesktop.org/show_bug.cgi?id=102475

--- Comment #6 from Olivier Fourdan <fourdan at xfce.org> ---
Well, what this patch does is disabling any specific grab handler if the
Xwayland grab protocol is not available, by postponing the setup of those
handler until Xwayland can bind to the relevant interface as advertised by the
compositor.

If the compositor doesn't support the Xwayland grab protocol, then all those
routines are not "enabled" in Xwayland, I don't see how they could break
anything if not used...

Unfortunately, we cannot tell whether or not the compositor supports the
Xwayland grab protocol using something like weston-info because, for security
reasons, the compositor will (should) only advertiset he given protocl to
Xwayland alone and hide it to any other client.

So, if that patch makes no difference, it means that:

 - The Wayland compositor claim to support Xwayland grab protocol but is buggy
and doesn't send all key events as expected

 - Or the problem is completely unrelated to this patch.

So next step for you is to:

 - Check the actual patches applied to mutter in Ubuntu
 - Check what happens at the protocol level

To do so, yo can use the envvar WAYLAND_DEBUG prior to start gnome-shell (which
will spawn Xwayland) so that we can tell what globals are listed in the
wl_registry and see if "zwp_xwayland_keyboard_grab_manager_v1" is one of them.

e.g., from a console:

  $ WAYLAND_DEBUG=1 dbus-run-session -- gnome-shell --display-server --wayland
|& tee ~/wayland-debug.log

The wl_registry globals will be listed at the beginning of the log so that
should be enough to tell if the compositor claims to be supporting
"zwp_xwayland_keyboard_grab_manager_v1".

Then, you can start qemu-kvm as usual and try to press the keys that do not
work, those will be captured in the log as well, so we can tell if the
compositor sends those key events to the client (Xwayland, in which case the
problem lies in Xwayland) or not (in which case the problem lies in the
compositor).

Please attach the "wayland-debug.log" to this bugzilla once you've performed
those tests (but make sure you don't type any sensitive data in any application
while the log is being captured as any key event will be logged).

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20170901/c3819dbe/attachment.html>


More information about the wayland-bugs mailing list