All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <1267520@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1267520] Re: Keyboard input not working when the "-k en-us" argument is specified.
Date: Wed, 17 Apr 2019 15:19:56 -0000	[thread overview]
Message-ID: <155551439607.13880.5653310165775565536.malone@gac.canonical.com> (raw)
In-Reply-To: 20140109160856.15157.6320.malonedeb@wampee.canonical.com

I think this is likely fixed with QEMU 4.0 by this commit here:

https://git.qemu.org/?p=qemu.git;a=commitdiff;h=26b1cbf8b65b3b55c3f

Could you please try again with QEMU 4.0-rc4 (or the final 4.0 release
next week)?

** Changed in: qemu
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1267520

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

Status in QEMU:
  Incomplete

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:
https://bugs.launchpad.net/qemu/+bug/1267520/+subscriptions

  parent reply	other threads:[~2019-04-17 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 16:08 [Qemu-devel] [Bug 1267520] [NEW] Keyboard input not working when the "-k en-us" argument is specified Mofi Taiwo
2014-01-09 16:31 ` [Qemu-devel] [Bug 1267520] " Mofi Taiwo
2014-01-09 17:08 ` Mofi Taiwo
2014-01-09 17:35 ` Mofi Taiwo
2014-01-10 15:48 ` Mofi Taiwo
2014-01-10 15:57 ` Mofi Taiwo
2014-01-10 16:05 ` Mofi Taiwo
2015-10-05 20:39 ` Andrew Oates
2016-12-15  7:45 ` Rowan Potgieter
2016-12-19  8:47 ` skovalev
2019-04-17 15:19 ` Thomas Huth [this message]
2019-06-17  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=155551439607.13880.5653310165775565536.malone@gac.canonical.com \
    --to=1267520@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.