http://bugzilla.suse.com/show_bug.cgi?id=1074144 Bug ID: 1074144 Summary: Xwayland environments lose keycode mapping, breaking spice keyboard Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: mlatimer@suse.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- When running under Wayland, keyboard mappings are lost through remote spice/vnc connections. This is easy to reproduce as follows: - Configure a Tumbleweed machine with Wayland - Connect to a remote virtualization host (ssh -X [host]) - Run virt-viewer to connect to a running virtual machine (virt-viewer [domain] - If the keyboard works, shut down virt-viewer, and restart it. - If the keyboard no longer works, the following messages are usually displayed in the terminal where virt-viewer was started:
(virt-viewer:113985): vnc-keymap-WARNING **: Unknown keycode mapping '(unnamed)'. Please report to gtk-vnc-list@gnome.org including the following information:
- Operating system - GDK build - X11 Server - xprop -root - xdpyinfo
(virt-viewer:113985): Gtk-WARNING **: Allocating size to SpiceDisplay 0xc54360 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? (virt-viewer:113985): GSpice-CRITICAL **: send_key: assertion 'scancode != 0' failed (virt-viewer:113985): GSpice-CRITICAL **: send_key: assertion 'scancode != 0' failed
Usually, the first time virt-viewer is started, the keyboard works. However, shutting down virt-viewer and restarting it will almost always result in a broken keyboard. Once in this state, the client machine (running Wayland) has to have X completely restarted in order to get back to a working state. This problem has been reported upstream (https://bugs.freedesktop.org/show_bug.cgi?id=99714), and there are several RedHat bugs on this issue. The most comprehensive is https://bugzilla.redhat.com/show_bug.cgi?id=1512564. -- You are receiving this mail because: You are on the CC list for the bug.