From: Benjamin Drung <bdrung@ubuntu.com>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 427612] Re: kvm sends caps lock key up event twice
Date: Sun, 28 Nov 2010 00:48:31 +0100 [thread overview]
Message-ID: <1290901711.2438.34.camel@deep-thought> (raw)
In-Reply-To: <4CEEC255.2020309@mail.berlios.de>
[-- Attachment #1: Type: text/plain, Size: 3196 bytes --]
Am Donnerstag, den 25.11.2010, 21:08 +0100 schrieb Stefan Weil:
> Am 24.11.2010 22:44, schrieb Benjamin Drung:
> > Attached a new version of my patch. You find two branches linked to this
> > bug for maverick and natty. The patch sets SDL_DISABLE_LOCK_KEYS and get
> > rid of the complete workaround in qemu-kvm. This requires SDL >= 1.2.14.
>
> For newer versions of SDL (those which use SDL_DISABLE_LOCK_KEYS
> to disable special handling of the lock keys), your patch looks ok.
> It is a working solution for maintainers of the latest Ubuntu releases.
>
> But what about older versions? For those, your patch will make QEMU's
> keyboard emulation unusable. Most older versions don't know
> SDL_DISABLE_LOCK_KEYS. As far as I know, some SDL versions (from Debian
> and Ubuntu) even used SDL_DISABLE_LOCK_KEYS with an inverted meaning.
>
> I don't think we can simply ignore old or incompatible versions of SDL.
> Therefore I suggest adding a runtime version check, so the emulation
> can either use the old code (SDL < 1.2.14) or your new code (SDL >= 1.2.14).
Yes, that's better than not supporting older SDL versions.
> The crucial point is whether "old" versions must be supported or not.
> This is something which the QEMU community should decide.
>
> > Stefan Weil wrote:
> >> 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.
> >
> > Addressed by new patch.
> >
> >> * 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).
> >
> > Addressed by new patch.
> >
> >> * The keyboard status LEDs and the qemu client's keyboard status
> >> can become unsynchronized if the input focus changes from qemu
> >> to other applications.
> >
> > Is this a regression of my patch or is it the case for the unpatched
> > qemu too?
>
> That is no regression, but a weakness which existed from the
> beginning. Your patch neither makes it better nor makes it worse.
I don't know if it can really fixed for all keyboard layout
combinations. Imagine using two keyboard layouts that have the caps lock
key mapped on different keys. How do you want to keep the caps lock
synchronized?
> > ** Patch added: "caps-lock-key-up-event-v2.patch"
> > https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/427612/+attachment/1743919/+files/caps-lock-key-up-event-v2.patch
>
> Just a small remark:
> Inline patches (instead of links) are preferred on qemu-devel
> because they make reading easier, and it's also easier for reviewers
> to add comments.
You request a new feature for Launchpad, because I used Launchpad to
attach my patch. Look at https://launchpad.net/bugs/427612 . All
comments for bugs in the qemu-kvm Ubuntu package are forwarded to the
mailing list.
--
Benjamin Drung
Ubuntu Developer (www.ubuntu.com) | Debian Maintainer (www.debian.org)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-11-27 23:48 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 ` [Qemu-devel] " Stefan Weil
2010-11-23 14:53 ` 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 [this message]
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=1290901711.2438.34.camel@deep-thought \
--to=bdrung@ubuntu.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).