qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>, Mike R <picnet@me.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] unknown keycodes
Date: Mon, 23 Apr 2018 10:42:51 +0100	[thread overview]
Message-ID: <20180423094251.GF3267@redhat.com> (raw)
In-Reply-To: <CAFEAcA9pJBRXTes8V8C0ka7_QYcehgPJzd6RNqGyktn7PLMKqg@mail.gmail.com>

On Mon, Apr 23, 2018 at 10:10:47AM +0100, Peter Maydell wrote:
> On 23 April 2018 at 04:31, Thomas Huth <thuth@redhat.com> wrote:
> > On 21.04.2018 11:27, Mike R wrote:
> >> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to qemu-devel@nongnu.org
> >>
> >> reported.
> >
> > Well, please also report:
> 
> It's kind of our own fault that we didn't ask for those
> sorts of details in that error message. I think that a lot
> of the time it was reported without necessarily meaning that
> any interesting keys weren't being handled correctly.
> 
> In any case, as of commit 2ec78706d188 that message has
> been removed, so the 2.12 release should fix this, or
> at least not produce unhelpful warnings :-)

Yes, if you get the same situation in 2.12, it will now print a much
better mesage:

        g_warning("Unknown X11 keycode mapping '%s'.\n"
                  "Please report to qemu-devel@nongnu.org\n"
                  "including the following information:\n"
                  "\n"
                  "  - Operating system\n"
                  "  - X11 Server\n"
                  "  - xprop -root\n"
                  "  - xdpyinfo\n",
                  keycodes ? keycodes : "<null>");


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-04-23  9:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  9:27 [Qemu-devel] unknown keycodes Mike R
2018-04-23  3:31 ` Thomas Huth
2018-04-23  9:10   ` Peter Maydell
2018-04-23  9:42     ` Daniel P. Berrangé [this message]
2018-04-23  9:44   ` Daniel P. Berrangé
  -- strict thread matches above, loose matches on Subject: below --
2015-04-16  9:44 Daniel Moyle
2012-01-12  8:56 Daniel Espling
2012-01-12 10:41 ` Daniel P. Berrange
2012-01-16  7:04   ` Daniel Espling
2012-01-16 11:34     ` Daniel P. Berrange
2013-05-07 21:02       ` Ali
2011-01-19  1:22 Henry Grebler
2011-01-19  1:45 ` Anthony Liguori
2009-06-21  8:56 [Qemu-devel] Unknown keycodes annonygmouse
2009-06-22 19:30 ` Anthony Liguori
2009-06-22 19:58   ` Andreas Färber

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=20180423094251.GF3267@redhat.com \
    --to=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=picnet@me.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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).