qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: B3r3n <B3r3n@argosnet.com>,
	qemu-discuss@nongnu.org,
	"Daniel P . Berrange" <berrange@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Qemu, VNC and non-US keymaps
Date: Mon, 11 May 2020 16:24:32 +0200	[thread overview]
Message-ID: <af732fbf-fd70-97bc-3ea8-25d66f5895de@redhat.com> (raw)
In-Reply-To: <E1jY9FF-0000Po-2c@lists.gnu.org>

Cc'ing more developers.

On 5/11/20 4:17 PM, B3r3n wrote:
> Dear all,
> 
> I am struggling for days/weeks with Qemu and its VNC accesses...with 
> non-US keymaps.
> 
> Let me summ the facts:
> - I am using a french keyboard over a Ubuntu 18.04.
> - I installed a simple Debian in a Qemu VM, configured with FR keyboard 
> (AZERTY).
> - I am launching the Qemu VM with the '-k fr' keymaping (original)
> - I tested with Qemu 3.1.1, 4.2.0 & 5.0.0.
> 
> I fail to have the AltGr keys, critical to frenches (pipe, backslash, 
> dash etc).
> checking with showkey, I see the keys arriving properly (29+56, 29+100, 
> etc).
> 
> Considering it might be a debian issue as well, I updated the 
> qemu/keymaps/fr file to have bar directly with the 6 key (normally bar 
> is AltGr + 6).
> For an unknown reason, the '6' then no longer works (showkey shows 
> nothing as well).
> 
> There might be something I miss, and the might also be some bug 
> somewhere, or some missings.
> For example, maybe X11 must be installed, even it unused (VNC client 
> connects to Qemu VNC port directly), or whatever.
> 
> Any help appreciated :-)
> 
> Thanks
> 
> Brgrds
> 
> 



       reply	other threads:[~2020-05-11 14:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1jY9FF-0000Po-2c@lists.gnu.org>
2020-05-11 14:24 ` Philippe Mathieu-Daudé [this message]
2020-05-11 14:31   ` Qemu, VNC and non-US keymaps LAHAYE Olivier
2020-05-11 15:11   ` Daniel P. Berrangé
2020-05-11 15:29     ` B3r3n
     [not found]     ` <20200511152957.6CFA8D1826@zmta04.collab.prod.int.phx2.redhat.com>
2020-05-11 17:19       ` Daniel P. Berrangé
2020-05-12  7:45         ` B3r3n
     [not found]         ` <20200512074530.8729D1892D3@zmta01.collab.prod.int.phx2.redhat.com>
2020-05-12  9:11           ` Daniel P. Berrangé
2020-05-12 16:30             ` B3r3n
2020-05-13  8:38             ` B3r3n
2020-05-13  8:42               ` Daniel P. Berrangé
2020-05-13  9:13                 ` B3r3n

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=af732fbf-fd70-97bc-3ea8-25d66f5895de@redhat.com \
    --to=philmd@redhat.com \
    --cc=B3r3n@argosnet.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@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 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).