From: Maximilian Hill <mhill@inett.de>
To: pve-user <pve-user@lists.proxmox.com>
Subject: [PVE-User] Keymap PVE 6.3-3
Date: Fri, 19 Feb 2021 15:39:49 +0100 [thread overview]
Message-ID: <YC/NtXunuEIBq8+X@inett.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 383 bytes --]
Hello,
I have 2 pve clusters, which I need to access through Citrx.
On these two clusters, something messes up the keymap pretty bad ([arrow down]
ends up as [enter] in the vm via the noVNC Console.
That's obviousely pretty bad, but works quite well with containers and
the pve node shell via term.js
Has someone experienced such problems before?
Best regards,
Maximilian Hil?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-02-19 14:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=YC/NtXunuEIBq8+X@inett.de \
--to=mhill@inett.de \
--cc=pve-user@lists.proxmox.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