Bug 89105 - spice-gtk suddenly starts sending escape characters instead of normal ones while using the keyboard
Summary: spice-gtk suddenly starts sending escape characters instead of normal ones wh...
Status: RESOLVED NOTOURBUG
Alias: None
Product: Spice
Classification: Unclassified
Component: spice-gtk (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Spice Bug List
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-12 13:54 UTC by Alberto Ruiz
Modified: 2015-02-20 12:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
spice stops sending any keystrokes to boxes (49.58 KB, text/plain)
2015-02-16 15:01 UTC, Alberto Ruiz 		Details
View All

Description Alberto Ruiz 2015-02-12 13:54:09 UTC 
Some times when switching to another window from Boxes using Alt-Tab (in my case, usually a terminal or Firefox), and then switching back to Boxes, suddenly boxes will not recognize my keystrokes anymore. Only when I get out of the Box (to the main Boxes overview) and open the Box again the problem goes away.

Funnily enough Ctrl+C works but if I just type normal characters it will send escape characters to the guest.

Not sure if related to this bug, but in one instance (this is harder to reproduce) the guest was cylcing between CapsLock and non-CapsLock so characters would ramdomly be upper case or lower case. I'd have a harder time suggestion how to reproduce this last behaviour.

Both the guest and the host are running Fedora Workstation 21.
Comment 1 Pavel Grunt 2015-02-16 10:32:46 UTC 
Hi, seems that the Ctrl key is stuck, but I can't reproduce. Please, add the spice debug log (SPICE_DEBUG=1 gnome-boxes).
Comment 2 Alberto Ruiz 2015-02-16 15:01:33 UTC 
Created attachment 113540 [details]
spice stops sending any keystrokes to boxes

I haven't been able to reproduce the blocked Ctrl key problem. But in this log I was not able to send any keystrokes to the guest.

Note the following warnings by the end of the log file:
(gnome-boxes:4750): GSpice-CRITICAL **: send_key: assertion 'scancode != 0' failed
(gnome-boxes:4750): GSpice-DEBUG: spice-widget.c:1339 key_event press: keycode: 39  state: 0  group 0 modifier 0

(gnome-boxes:4750): GSpice-CRITICAL **: send_key: assertion 'scancode != 0' failed
(gnome-boxes:4750): GSpice-DEBUG: spice-widget.c:1339 key_event press: keycode: 40  state: 0  group 0 modifier 0
Comment 3 Pavel Grunt 2015-02-16 15:49:36 UTC 
Thanks for the log, keys were not send to the guest because of this:

 (gnome-boxes:4750): vnc-keymap-WARNING **: Unknown keycode mapping '(null)'

What is your keyboard mapping, can you give me output of setxkbmap -print
Comment 4 Alberto Ruiz 2015-02-16 15:54:53 UTC 
xkb_keymap {
	xkb_keycodes  { include "evdev+aliases(qwerty)"	};
	xkb_types     { include "complete"	};
	xkb_compat    { include "complete"	};
	xkb_symbols   { include "pc+us+inet(evdev)"	};
	xkb_geometry  { include "pc(pc105)"	};
};

Note though, these spurious input problems with happen out of the blue, without any sort of explicit changes in the input configuration.
Comment 5 Pavel Grunt 2015-02-16 16:50:57 UTC 
Are you on wayland?
Can you try reproduce it using spice-gtk only (with spicy) or with remote-viewer / virt-viewer ?
Comment 6 Pavel Grunt 2015-02-20 12:53:14 UTC 
It is probably a bug in XWayland - XkbGetKeyboard always returns NULL.
 
Workaround: http://lists.freedesktop.org/archives/spice-devel/2015-February/018964.html

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.