From: Dustin Kirkland <kirkland@canonical.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kwolf@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
shaharh@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Qemu does not pass pressed caps lock to client
Date: Fri, 12 Feb 2010 14:49:55 -0600 [thread overview]
Message-ID: <1266007795.12609.58.camel@x200> (raw)
In-Reply-To: <4B75A193.8040202@codemonkey.ws>
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
On Fri, 2010-02-12 at 12:44 -0600, Anthony Liguori wrote:
> On 02/12/2010 12:17 PM, Paolo Bonzini wrote:
> > On 02/12/2010 04:15 PM, Anthony Liguori wrote:
> >>
> >> So basically, Debian carries a hacked version of SDL that changes the
> >> key press behaviour?
> >
> > Yes, the patch was submitted to not change the default but the
> > maintainer thought he knew better. Or confused an == with a != more
> > likely.
> >
> >> That's a Debian/Ubuntu bug. Shame on them for changing the behaviour of
> >> a library API like that.
> >
> > Indeed. Maybe the Debian/Ubuntu maintainers for QEMU and KVM will
> > read this thread and make a fuss.
>
> I've already updated the bug report appropriately. Dustin, the ball's
> in your court :-)
I looked at the original Debian Bug,
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=317010
The libsdl1.2 package in Ubuntu is no longer carrying that patch,
debian/patches/005_lock_keys.diff. So I don't think that's quite the
cause of this.
As for reproducing the bug, eventually, I was able to get my host and
guest caps-lock keys out of sync, if I went back and forth, between
guest and host, toggling caps-lock. What's the desired behavior here?
I don't have much of an opinion (other than that the caps-lock key is a
waste of valuable keyboard real estate, that I never actually use on
purpose, only ever hitting it accidentally and causing problems :-)
:-Dustin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-02-12 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 21:13 [Qemu-devel] Qemu does not pass pressed caps lock to client Shahar Havivi
2010-02-12 9:54 ` Kevin Wolf
2010-02-12 11:09 ` Shahar Havivi
2010-02-12 11:43 ` Kevin Wolf
2010-02-12 12:39 ` [Qemu-devel] " Paolo Bonzini
2010-02-12 15:15 ` Anthony Liguori
2010-02-12 18:17 ` Paolo Bonzini
2010-02-12 18:44 ` Anthony Liguori
2010-02-12 20:49 ` Dustin Kirkland [this message]
2010-02-13 11:21 ` 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=1266007795.12609.58.camel@x200 \
--to=kirkland@canonical.com \
--cc=anthony@codemonkey.ws \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shaharh@gmail.com \
/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.