From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, shaharh@gmail.com
Subject: [Qemu-devel] Re: Qemu does not pass pressed caps lock to client
Date: Sat, 13 Feb 2010 12:21:11 +0100 [thread overview]
Message-ID: <4B768B27.6070203@redhat.com> (raw)
In-Reply-To: <1266007795.12609.58.camel@x200>
On 02/12/2010 09:49 PM, Dustin Kirkland wrote:
> 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.
The bug was reported in Karmic, which still has the patch with s/005/205/.
Paolo
prev parent reply other threads:[~2010-02-13 11:21 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
2010-02-13 11:21 ` Paolo Bonzini [this message]
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=4B768B27.6070203@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@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 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).