From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thorsten Glaser <t.glaser@tarent.de>
Cc: qemu-devel@nongnu.org
Subject: Re: qemu-system-x86_64: warning: Unknown X11 keycode mapping '<null>'.
Date: Mon, 2 Mar 2020 10:28:41 +0000 [thread overview]
Message-ID: <20200302102841.GD1679990@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2003020002570.23029@tglase.lan.tarent.de>
On Mon, Mar 02, 2020 at 12:04:46AM +0100, Thorsten Glaser wrote:
> I got this while running qemu under VNC, and was told to report it.
>
> including the following information:
>
> - Operating system
> Debian GNU/Linux sid/x32
> - X11 Server
> x11vnc 0.9.16-3
Can you tell me a bit more detail about how you launch this all.
"x11vnc" suggests you had a regular X11 desktop session, and are
exporting it via VNC ?
But later...
> - xdpyinfo
> name of display: :2
> version number: 11.0
> vendor string: AT&T Laboratories Cambridge
...this suggests your running a VNC server, with embedded X11 server
> - xprop -root
...there's no _XKB_RULES_NAMES(STRING) property listed, which is the key
thing we'd expect to see for a modern X server. eg
_XKB_RULES_NAMES(STRING) = "evdev", "pc105", "us", "", ""
is what most X servers on Linux will report.
Can you also say what QEMU version ?
QEMU since 2.12.0 or later has a second way to detect the keymap, by
querying the scancode mapping for certain keys.
So either your QEMU is fairly old, or you are using a keycode mapping
that QEMU has no understanding of (we support evdev, or the classic
xfree86 'kbd' mapping). It would be highly unusual not to use one of
those two, but none the less, that appears to be the case here ?
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 :|
next prev parent reply other threads:[~2020-03-02 10:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-01 23:04 qemu-system-x86_64: warning: Unknown X11 keycode mapping '<null>' Thorsten Glaser
2020-03-02 10:28 ` Daniel P. Berrangé [this message]
2020-03-02 12:43 ` Thorsten Glaser
2020-03-02 13:03 ` Daniel P. Berrangé
2020-03-02 18:19 ` Thorsten Glaser
2020-03-03 10:46 ` Daniel P. Berrangé
2020-03-03 10:44 ` Daniel P. Berrangé
2020-03-03 13:12 ` Thorsten Glaser
2020-03-03 13:14 ` Daniel P. Berrangé
-- strict thread matches above, loose matches on Subject: below --
2020-02-26 23:31 Oliver Bailey
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=20200302102841.GD1679990@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=t.glaser@tarent.de \
/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).