qemu-devel
[Top][All Lists]
Advanced

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

[Qemu-devel] [Bug 1258626] Re: Curses Keyboard Broken On OS X


From: James Clarke
Subject: [Qemu-devel] [Bug 1258626] Re: Curses Keyboard Broken On OS X
Date: Fri, 06 Dec 2013 19:18:58 -0000

EDIT: I should have mentioned that this is using QEMU 1.6.1, but the
problem also occurs with 1.3.1. Also, in case it makes a difference, I
installed QEMU using Homebrew.

** Description changed:

  Whenever I run ``qemu-system-i386 -curses ...'' (with or without a ``-k
  en-gb'') on OS X 10.9, the keyboard does not work properly. For example,
  when attempting to switch to the QEMU console with Alt+2, I get:
  
  ``Warning: no scancode found for keysym 226
  Warning: no scancode found for keysym 130
  Warning: no scancode found for keysym 172''
  
  I have checked and these scancodes are not mentioned in
- ``share/qemu/keymaps/''.
+ ``share/qemu/keymaps/''. This is using QEMU 1.6.1, but the problem also
+ occurs with 1.3.1. Also, in case it makes a difference, I installed QEMU
+ using Homebrew.

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

Title:
  Curses Keyboard Broken On OS X

Status in QEMU:
  New

Bug description:
  Whenever I run ``qemu-system-i386 -curses ...'' (with or without a
  ``-k en-gb'') on OS X 10.9, the keyboard does not work properly. For
  example, when attempting to switch to the QEMU console with Alt+2, I
  get:

  ``Warning: no scancode found for keysym 226
  Warning: no scancode found for keysym 130
  Warning: no scancode found for keysym 172''

  I have checked and these scancodes are not mentioned in
  ``share/qemu/keymaps/''. This is using QEMU 1.6.1, but the problem
  also occurs with 1.3.1. Also, in case it makes a difference, I
  installed QEMU using Homebrew.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1258626/+subscriptions



reply via email to

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