https://bugs.kde.org/show_bug.cgi?id=440340

            Bug ID: 440340
           Summary: keyboard combinations not captured by guest OS
                    (kwin_wayland issue?)
           Product: kwin
           Version: 5.22.2
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Keywords: wayland
          Severity: normal
          Priority: NOR
         Component: platform-wayland
          Assignee: kwin-bugs-n...@kde.org
          Reporter: bughunt...@gmail.com
  Target Milestone: ---

SUMMARY


STEPS TO REPRODUCE
1. Start a VM in VirtualBox while using 'kwin_wayland' on the host rather than
'kwin_x11'.
2. Click inside the VM to make sure it's the active window.
3. Press the combination Meta+E on the keyboard.

OBSERVED RESULT
Observe that keyboard combinations such as Meta+E are processed by the host
rather than by the guest.


EXPECTED RESULT
The VM (the guest) should process the keyboard combination, and it should have
no effect on the host.


SOFTWARE/OS VERSIONS
Linux: kernel 5.12.14
KDE Plasma Version: 5.22.2
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

In VirtualBox, keyboard combinations trigger shortcuts on the host machine
rather than in the VM's guest OS.
This doesn't occur when the host is using 'kwin_x11'.
It only happens with 'kwin_wayland'.
(Think of keyboard combinations like Meta+E to open the file manager.)

>From what I know, this is in some sense normal on Wayland since Wayland is more
secure. But, as you're probably aware, in recent years Wayland has provided
extensions so that well-behaved programs can grab the keyboard if they wish.

Of course, it may be a VirtualBox bug, so I looked into a that:

Currently, VirtualBox tries to be well-behaved, because it is sending the
'_XWAYLAND_MAY_GRAB_KEYBOARD' message ( see
https://www.virtualbox.org/ticket/19650 ). This helps it grab the keyboard on
mutter (GNOME's Wayland compositor).

However, that virtualbox fix seems specific to mutter, and doesn't appear to
help for kwin (or 'kwin_wayland').

Questions:

  - Is there anything else VirtualBox needs to do to properly grab the
keyboard?

    Is there some 'standard' method? One that works on both 'kwin_wayland' and
'mutter'?
    Or is the '_XWAYLAND_MAY_GRAB_KEYBOARD' message the standard way?
    That message seems to be mutter-specific, but I could be wrong.

  - Or, should kwin listen for the above message and handle it properly?

    If so, consider this to be a feature request.

Related:

  vbox: https://www.virtualbox.org/ticket/19650
  kwin: https://phabricator.kde.org/T12988
  kwin: https://bugs.kde.org/show_bug.cgi?id=405877
  mutter: https://bugzilla.redhat.com/show_bug.cgi?id=1285770

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to