All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Warner Losh <imp@bsdimp.com>
Cc: qemu-devel@nongnu.org,
	"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	kraxel@redhat.com
Subject: Re: [Qemu-devel] It told me to report this...
Date: Wed, 13 Dec 2017 09:31:58 +0000	[thread overview]
Message-ID: <20171213093158.GC28379@redhat.com> (raw)
In-Reply-To: <20171211150841.GE23622@redhat.com>

On Mon, Dec 11, 2017 at 03:08:41PM +0000, Daniel P. Berrange wrote:
> On Mon, Dec 11, 2017 at 08:05:29AM -0700, Warner Losh wrote:
> > On Mon, Dec 11, 2017 at 5:33 AM, Daniel P. Berrange <berrange@redhat.com>
> > wrote:
> > 
> > > On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote:
> > > > * Warner Losh (imp@bsdimp.com) wrote:
> > > > > unknown keycodes `empty+aliases(qwerty)', please report to
> > > > > qemu-devel@nongnu.org
> > > > >
> > > > > My X server is Mac XQuartz 2.7.11. I saw this question raised several
> > > years
> > > > > ago in the archives, with promises of patches, but couldn't find
> > > anything
> > > > > relevant in the latest tree I grabbed from github (I saw this problem
> > > there
> > > > > as well as 2.9.0 installed from FreeBSD ports).
> > > > >
> > > > > What's my next step here?
> > > >
> > > > I think that's one of Gerd's messages, so I've added him to the
> > > > email and also Daniel since he's got an interest in key mappings.
> > > >
> > > > Have you any idea if it happened when you pressed a particular key?
> > >
> > > Don't worry, this is a known limitation of the current X backend for QEMU.
> > >
> > > It only knows how to work with Xorg on Linux with kbd or evdev. It can't
> > > cope with OS-X or Windows  X11 servers yet. I've got patches that will
> > > address this which i hope to finally put into 2.12 as part of the
> > > keycodemapdb
> > > work.
> > >
> > 
> > I've built qemu many times over the years. I'd be happy to test them out to
> > make sure they work for me :). Also, a million years ago, I did extensive
> > work with X11 keymaps when I was working on the OI toolkit, so I have some
> > familiarity...
> 
> I'm basically copying the same code / approach we've already done with
> GTK-VNC & SPICE-GTK
> 
> I've got a patch here:
> 
>   https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02058.html
> 
> but that almost certainly won't apply to current GIT master, so I'll be
> sending updated versions soonish.

If you want to test something, then I've posted new patch series with
the UI changes:

  https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg01988.html

it applies to current git master, aka soon to be 2.11.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

  reply	other threads:[~2017-12-13  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-10 21:26 [Qemu-devel] It told me to report this Warner Losh
2017-12-11 12:29 ` Dr. David Alan Gilbert
2017-12-11 12:33   ` Daniel P. Berrange
2017-12-11 15:05     ` Warner Losh
2017-12-11 15:08       ` Daniel P. Berrange
2017-12-13  9:31         ` Daniel P. Berrange [this message]
2017-12-11 15:06   ` Warner Losh
2017-12-11 15:10     ` Daniel P. Berrange

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=20171213093158.GC28379@redhat.com \
    --to=berrange@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=imp@bsdimp.com \
    --cc=kraxel@redhat.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 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.