qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Bug 427612 <427612@bugs.launchpad.net>
Cc: Benjamin Drung <benjamin.drung@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 427612] Re: kvm sends caps lock key up event twice
Date: Tue, 23 Nov 2010 20:03:32 +0100	[thread overview]
Message-ID: <4CEC1004.4090105@mail.berlios.de> (raw)
In-Reply-To: <20101123004254.824.65473.malone@gandwana.canonical.com>

Am 23.11.2010 01:42, schrieb Benjamin Drung:
> Attached the patch for qemu-kvm 0.13. This patch is tested on natty with
> qemu-kvm 0.13.0+noroms-0ubuntu7 and the German and NEO2 keyboard layout.
>
> ** Patch added: "caps-lock-key-up-event.patch"
> https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/427612/+attachment/1742131/+files/caps-lock-key-up-event.patch
>
> ** Changed in: qemu
> Status: Invalid => New
>

The patch might fix part of the problem, but there remain more issues:

* SDL also sends an SDL_KEYUP event for caps lock when the
   environment variable SDL_DISABLE_LOCK_KEYS is set.
   This mode is very useful but currently unsupported by qemu/kvm.

* Num lock and caps lock are handled in a similar way by SDL.
   The patch only handles caps lock. Maybe this is less important
   because keyboard layouts which remap num lock are rare
   (I don't know any).

* The keyboard status LEDs and the qemu client's keyboard status
   can become unsynchronized if the input focus changes from qemu
   to other applications.

Regards,

Stefan Weil

  parent reply	other threads:[~2010-11-23 19:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090910235343.14184.29717.malonedeb@gangotri.canonical.com>
2010-05-21 11:55 ` [Qemu-devel] [Bug 427612] Re: does not pass pressed caps lock to client Launchpad Bug Tracker
2010-06-02 20:12 ` Anthony Liguori
2010-11-17 23:52 ` Benjamin Drung
2010-11-17 23:55 ` Benjamin Drung
2010-11-18  1:50 ` Serge Hallyn
2010-11-18  1:56 ` Serge Hallyn
2010-11-18 23:46 ` [Qemu-devel] [Bug 427612] Re: kvm sends caps lock key up event twice Benjamin Drung
2010-11-19  3:20   ` [Qemu-devel] " Serge Hallyn
2010-11-18 23:47 ` [Qemu-devel] " Benjamin Drung
2010-11-19  3:19   ` [Qemu-devel] " Serge Hallyn
2010-11-19  9:26 ` [Qemu-devel] " Benjamin Drung
2010-11-19 13:52 ` Serge Hallyn
2010-11-23  0:42 ` Benjamin Drung
2010-11-23 14:30   ` [Qemu-devel] " Serge Hallyn
2010-11-23 19:03   ` Stefan Weil [this message]
2010-11-23 14:53 ` [Qemu-devel] " Serge Hallyn
2010-11-24 21:13 ` Launchpad Bug Tracker
2010-11-24 21:15 ` Benjamin Drung
2010-11-24 21:23 ` Launchpad Bug Tracker
2010-11-24 21:44 ` Benjamin Drung
2010-11-25 20:08   ` Stefan Weil
2010-11-27 23:48     ` Benjamin Drung
2011-02-03 21:35       ` [Qemu-devel] [PATCH 0.14] ui/sdl: Fix handling of caps lock and num lock keys Stefan Weil
2011-02-04 12:51         ` Anthony Liguori
2010-11-24 23:31 ` [Qemu-devel] [Bug 427612] Re: kvm sends caps lock key up event twice Serge Hallyn
2010-11-25 23:45 ` Launchpad Bug Tracker
2010-11-25 23:50 ` Benjamin Drung
2010-12-03 16:15 ` Martin Pitt
2010-12-03 17:51 ` Launchpad Bug Tracker
2010-12-03 23:21 ` Benjamin Drung
2010-12-04 11:41 ` Jean-Baptiste Lallement
2010-12-09 10:55 ` Launchpad Bug Tracker
2012-09-14  9:00 ` Paolo Bonzini

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=4CEC1004.4090105@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=427612@bugs.launchpad.net \
    --cc=benjamin.drung@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).