Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1553193 - Xwayland reports keycode mapping 'unnamed', messes up spice VM keyboard
Summary: Xwayland reports keycode mapping 'unnamed', messes up spice VM keyboard
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gtk-vnc
Version: 7.5
Hardware: All
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Daniel Berrangé
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-08 13:28 UTC by Olivier Fourdan
Modified: 2019-08-02 17:01 UTC (History)
31 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1512564
Environment:
Last Closed: 2019-08-02 17:01:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Olivier Fourdan 2018-03-08 13:28:52 UTC 
+++ This bug was initially created as a clone of Bug #1512564 +++

Description of problem:
Same as bug 1540056, gtk-vnc has the same code and requires the same fix.

When running on Xwayland, the keycode mapping property is not available,
which causes unknown keycode mapping errors and the keyboard doesn't
work.

Version-Release number of selected component (if applicable):
gtk-vnc

How reproducible:
100%

Steps to Reproduce:
1. Run virt-manager with X11 backend under Wayland/Xwayland
   GDK_BACKEND=x11 virt-manager

2. Connect to a virtual machine using VNC

Actual results:
1. I can't input user name and password on login page.
2. I can input with keyboard for vnc guest.

Expected results:
Keyboard works.

Additional info:

A patch for gtk-vnc has been posted to address this issue in bug 1512564
Comment 5 Christophe Fergeau 2018-06-18 15:52:18 UTC 
This is fixed upstream by https://gitlab.gnome.org/GNOME/gtk-vnc/commit/8dee84bfd34cc88d41e98bdc9d7ac9f0f226644f
Note You need to log in before you can comment on or make changes to this bug.