[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 1267520] Re: Keyboard input not working when the "-k e

From: Rich Fletcher
Subject: [Qemu-devel] [Bug 1267520] Re: Keyboard input not working when the "-k en-us" argument is specified.
Date: Fri, 30 May 2014 01:45:07 -0000

I think I stumbled on this bug.  I was using packer to generate qemu-
based virtual machines, and identical configurations would fail
(complaining about invalid keymaps when keystrokes were sent) depending
on where the current directory was.  It doesn't work if qemu is run from
a directory containing a directory named "common".

Guessing this is related to qemu_find_file, maybe
#diff-48a342a3d278d5bdcc69db8f9758dcd6 .

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  Keyboard input not working when the "-k en-us" argument is specified.

Status in QEMU:

Bug description:
  This bug occurs on qemu compiled with i386_softmmu and x86-64_softmmu on 
linux kernel 3.5.0 (64-bit). (Haven't confirmed this for other targets).
  Whenever I run qemu (both i386 and x86_64) to use the en-us language (even 
though it is the default), I get "Warning: no scancode found for keysym X" (X 
is an integer).
  In the disk image I need qemu to run, I had a shell set up.  The shell 
doesn't register keyboard input when the '-k en-us' command line argument is 
set to run qemu. I did not have this problem with earlier versions of qemu.

  Additional information:
  Setting keymaps directory on command line -L doesn't resolve this.
  Bug occurs with on both curses and sdl VGA output.
  I am running qemu on Ubuntu 12.04 and I have not been able see if the bug is 
distribution-specific. However, I am also experiencing the bug on Kali-Linux; 
another debian based distribution.
  It turns out that all languages reproduce the bug, not just 'en-us'.

  Update: I have narrowed the bug to be attributable to versions later
  than qemu-1.1.2.

  Here's a listing of key being mapped:

  Setting keysym exclam (33) to 258
  Setting keysym at (64) to 259
  Setting keysym numbersign (35) to 260
  Setting keysym dollar (36) to 261
  Setting keysym percent (37) to 262
  Setting keysym asciicircum (94) to 263
  Setting keysym ampersand (38) to 264
  Setting keysym asterisk (42) to 265
  Setting keysym parenleft (40) to 266
  Setting keysym parenright (41) to 267
  Setting keysym minus (45) to 12
  Setting keysym underscore (95) to 268
  Setting keysym equal (61) to 13
  Setting keysym plus (43) to 269
  Setting keysym bracketleft (91) to 26
  Setting keysym braceleft (123) to 282
  Setting keysym bracketright (93) to 27
  Setting keysym braceright (125) to 283
  Setting keysym semicolon (59) to 39
  Setting keysym colon (58) to 295
  Setting keysym apostrophe (39) to 40
  Setting keysym quotedbl (34) to 296
  Setting keysym grave (96) to 41
  Setting keysym asciitilde (126) to 297
  Setting keysym backslash (92) to 43
  Setting keysym bar (124) to 299
  Setting keysym comma (44) to 51
  Setting keysym less (60) to 307
  Setting keysym period (46) to 52
  Setting keysym greater (62) to 308
  Setting keysym slash (47) to 53
  Setting keysym question (63) to 309

  As one can see, the pc-bios/keymaps/common, contaning the QWWERTY
  keys, is not processed in parse_init_keyboard at ui/keymaps.c even
  though the XKB map (keymaps/en-us) includes the file.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]