RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1537525 - cannot use keyboard in virtual machines
Summary: cannot use keyboard in virtual machines
Keywords:
Status: CLOSED DUPLICATE of bug 1540056
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spice-gtk
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Default Assignee for SPICE Bugs
QA Contact: SPICE QE bug list
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-23 12:48 UTC by Vladimir Benes
Modified: 2018-02-06 16:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-06 15:05:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Vladimir Benes 2018-01-23 12:48:38 UTC 
Description of problem:
I cannot use keyboard in virtual machines (in both Virt-manager and Boxes). I've tried F25, RHEL7.3 and Windows 10. All behave the same. Mouse works but keyboard does not.

Version-Release number of selected component (if applicable):
libwayland-client-1.14.0-2.el7.x86_64
kernel-3.10.0-831.el7.x86_64
qemu-kvm-1.5.3-153.el7.x86_64
gnome-boxes-3.22.4-4.el7.x86_64
virt-manager-1.4.3-3.el7.noarch


Additional info:
There are other issues in gnome-boxes like invisible cursor on app decorator, etc, not sure if these issues are related.
Comment 1 Olivier Fourdan 2018-02-06 13:39:01 UTC 
Note, “wayland” (the component) is a small RPC library, this issue cannot be in “Wayland”.

So we need to first identify where this issue belongs.

What you describe looks a lot like bug 1534324 which is a bug in the way spice-gtk or gtk-vnc try to detect the scancodes. The original bug report for Fedora is bug 1479682.

This can be seen if for you get erros like:

   WARNING **: Unknown X11 keycode mapping '(unnamed)'.

When typing on the keyboard.

This issue happens when using X11 as the backend for those applications, whereas when used with the Wayland backend no such issue occurs.

The way gtk+ works, it will try the Wayland backend first, it that fails, it fallbacks automatically to the X11 backend. This can happen for example when running via “ssh -X” or when running as a different user (“sudo ...” or “su ...”)

Can you check iy you get the “Unknown X11 keycode mapping '(unnamed)'” warniong and if you're using the X11 backend instead of the Wayland native one?
Comment 2 Olivier Fourdan 2018-02-06 14:00:29 UTC 
(Note: there is a funny test to check which backend a given window is using, run xeyes and hover the window, if the eyes follow your pointer while it moves over the window, then it's using X11, if the eyes remain completely static, then it's using Wayland)
Comment 3 Vladimir Benes 2018-02-06 14:14:41 UTC 
I can see this:
(gnome-boxes:7272): vnc-keymap-WARNING **: Unsupported GDK Windowing platform.
Disabling extended keycode tables.
Please report to gtk-vnc-list
including the following information:

  - Operating system
  - GDK Windowing system build

(gnome-boxes:7272): GSpice-CRITICAL **: send_key: assertion 'scancode != 0' failed

(gnome-boxes:7272): GSpice-CRITICAL **: spice_gtk_session_request_auto_usbredir: assertion 's->auto_usbredir_reqs > 0' failed


First critical appears upon every single key hit the second one upon disconnecting from the box.

I can see those processes:
vbenes    5966  0.0  0.0 290928  2884 tty2     Ssl+ 15:03   0:00 /usr/libexec/gdm-wayland-session gnome-session
vbenes    6064  0.5  0.3 364108 72988 tty2     Sl+  15:03   0:02 /usr/bin/Xwayland :1 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6


anyhting more to post here?
Comment 4 Vladimir Benes 2018-02-06 14:18:49 UTC 
eyes are following me... 

but I checked Wayland session in gdm..
Comment 5 Vladimir Benes 2018-02-06 14:31:29 UTC 
DESKTOP_SESSION=gnome-wayland
XDG_SESSION_TYPE=wayland
GDMSESSION=gnome-wayland
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
XDG_SESSION_DESKTOP=gnome-wayland
Comment 6 Olivier Fourdan 2018-02-06 14:59:03 UTC 
Vladimir Benes from comment #3)
> I can see this:
> (gnome-boxes:7272): vnc-keymap-WARNING **: Unsupported GDK Windowing
> platform.

How do you start/run gnome-boxes? I don't see that warning here...

> Disabling extended keycode tables.
> Please report to gtk-vnc-list
> including the following information:
> 
>   - Operating system
>   - GDK Windowing system build
> 
> (gnome-boxes:7272): GSpice-CRITICAL **: send_key: assertion 'scancode != 0'
> failed

This is the same as bug 1534324, bug 1540056 and bug 1479682, that's why the keyboard doesn't work.

(In reply to Vladimir Benes from comment #4)
> eyes are following me... 
> 
> but I checked Wayland session in gdm..

Yes, you are running GNOME/Wayland but that doesn;t mean that all your applications are using Wayland.

Wayland is a entirely different protocol from X11, applications needs to be rewritten or ported to be able to use Wayland. For those not able to “talk” Wayland natively, we provide Xwayland, which is a Wayland client and an X11 server for those applications only talking X11.

So, running a Wayland sessio ndoes nto mean that all your applications are using Wayland...

(In reply to Vladimir Benes from comment #5)
> DESKTOP_SESSION=gnome-wayland
> XDG_SESSION_TYPE=wayland
> GDMSESSION=gnome-wayland
> GNOME_DESKTOP_SESSION_ID=this-is-deprecated
> XDG_SESSION_DESKTOP=gnome-wayland

Again, I have no doubt you selected “GNOME Wayland” session, does not mean that all your apps are able to run on Wayland.
Comment 7 Olivier Fourdan 2018-02-06 15:05:12 UTC 

*** This bug has been marked as a duplicate of bug 1540056 ***
Comment 8 Vladimir Benes 2018-02-06 15:11:30 UTC 
(In reply to Olivier Fourdan from comment #6)
> Vladimir Benes from comment #3)
> > I can see this:
> > (gnome-boxes:7272): vnc-keymap-WARNING **: Unsupported GDK Windowing
> > platform.
> 
> How do you start/run gnome-boxes? I don't see that warning here...
> 
gnome-boxes command in gnome-terminal

> > Disabling extended keycode tables.
> > Please report to gtk-vnc-list
> > including the following information:
> > 
> >   - Operating system
> >   - GDK Windowing system build
> > 
> > (gnome-boxes:7272): GSpice-CRITICAL **: send_key: assertion 'scancode != 0'
> > failed
> 
> This is the same as bug 1534324, bug 1540056 and bug 1479682, that's why the
> keyboard doesn't work.
> 
are we close to a solution in any of those?
Comment 9 Tomas Pelka 2018-02-06 16:01:25 UTC 
(In reply to Vladimir Benes from comment #8)
> (In reply to Olivier Fourdan from comment #6)
> > Vladimir Benes from comment #3)
> > > I can see this:
> > > (gnome-boxes:7272): vnc-keymap-WARNING **: Unsupported GDK Windowing
> > > platform.
> > 
> > How do you start/run gnome-boxes? I don't see that warning here...
> > 
> gnome-boxes command in gnome-terminal
> 
> > > Disabling extended keycode tables.
> > > Please report to gtk-vnc-list
> > > including the following information:
> > > 
> > >   - Operating system
> > >   - GDK Windowing system build
> > > 
> > > (gnome-boxes:7272): GSpice-CRITICAL **: send_key: assertion 'scancode != 0'
> > > failed
> > 
> > This is the same as bug 1534324, bug 1540056 and bug 1479682, that's why the
> > keyboard doesn't work.
> > 
> are we close to a solution in any of those?

We are not, moved to 7.6.
Note You need to log in before you can comment on or make changes to this bug.