All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org, James Barrett <xucaen@gmail.com>
Subject: Re: [Qemu-devel] qemu warnings and errors
Date: Tue, 20 Feb 2018 14:49:38 +0000	[thread overview]
Message-ID: <20180220144938.GL6021@redhat.com> (raw)
In-Reply-To: <869bcfe6-8199-d7fa-7193-4bb17f6d6ca7@redhat.com>

On Tue, Feb 20, 2018 at 08:45:00AM -0600, Eric Blake wrote:
> On 02/20/2018 02:38 AM, Gerd Hoffmann wrote:
> >    Hi,
> > 
> > > What version of QEMU?
> > > 
> > > > unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
> > > 
> > > This part is the only part that urges you to report the error, but I
> > > don't know much about what's going on here.
> > > 
> > > Maybe Gerd knows?
> > 
> > We had lots of keymap/keycode changes recently, most likely this will be
> > fixed in 2.12, maybe it already is in 2.11.  So, when using something
> > older, try upgrading first (or just ignore it in case it happes to be a
> > key you don't need).
> 
> The error message doesn't mention a numeric code or other way to figure out
> which key is problematic.  While this particular message may disappear when
> you upgrade, it would also be worth investigating if this message can give
> more details to figure out which keycode is problematic in case of future
> mismatches, other than just "unnamed".

It isn't about a specific key. This message is basically saying we don't
know what keymapping the X server is using, so we've given up. Historically
QEMU could only identify evdev and/or kbd key mappings. With the newly
merged code, we can now detect many more especially including Windows and
OS-X X11 server mappings. So git master hopefully removed the most common
cases that would trigger this particular error message. There's probably
still some remaining though, as there's a huge range of X11 servers impls
in the world.  With current git master this message will instruct the user
to provide us a list of relevant info to help us diagnose it - see the
end of ui/x_keymap.c file.

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:[~2018-02-20 14:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 15:24 [Qemu-devel] qemu warnings and errors James Barrett
2018-02-19 19:27 ` John Snow
2018-02-20  8:38   ` Gerd Hoffmann
2018-02-20 14:45     ` Eric Blake
2018-02-20 14:49       ` Daniel P. Berrangé [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=20180220144938.GL6021@redhat.com \
    --to=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xucaen@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.