All of lore.kernel.org
 help / color / mirror / Atom feed
From: B3r3n <B3r3n@argosnet.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: B3r3n <B3r3n@argosnet.com>,
	"Philippe Mathieu-Daudà ? ©" <philmd@redhat.com>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Gerd Hoffmann" <kraxel@redhat.com>,
	qemu-discuss@nongnu.org
Subject: Re: Qemu, VNC and non-US keymaps
Date: Tue, 12 May 2020 18:30:16 +0200	[thread overview]
Message-ID: <E1jYXnT-00051X-HL@lists.gnu.org> (raw)
In-Reply-To: <20200512091106.GH1191162@redhat.com>

Dear all,

>VNC == RFB - they're two different terms of the same thing.
>
>The core RFB/VNC protocol only knows about keysyms.
Ok, so RFB is not the keyword to track :-(

>AFAIK,  TightVNC doesn't support the scancode extension, only TigerVNC.
Confirmed, I replaced TightVNC viewer by TigerVNC, solves the issue. 
I got AltGr working + Ctrl_R acting as AltGr (my Debian kbd definition).
With this client, it is fine.

About this issue:
> > I realize that AltGr is sending 29+100 (seen via showkey), when CTRL_R only
> > sends 97.
> > When using a remote console (iLo and iDRAC), AltGr only sends 100.
> >
> > I wonder if the issue would not also be the fact AltGr sends 2 codes, still
> > another one to select the character key (6 for example).
> >
> > Is that normal Qemu is transforming AltGr (100) in 29+100 ?
>
>It is hard to say without seeing debuging to see what QEMU received.

I saw Qemu must be compile with debug support, ok.
 From this, if you have a recommendation, specific config to setup to 
debug the particular keyboard, I can do that.

To me the issue is here since a single keyboard key should produce a 
single keycode. Since my PC does not send 2 keys (else TigerVNC or 
noVNC would behave the same), it is elsewhere...

Thanks

Brgrds



  reply	other threads:[~2020-05-12 16:34 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 ` Qemu, VNC and non-US keymaps Philippe Mathieu-Daudé
2020-05-11 14:31   ` 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 [this message]
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=E1jYXnT-00051X-HL@lists.gnu.org \
    --to=b3r3n@argosnet.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=philmd@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 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.