From: Darren Blaber <1895219@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1895219] Re: qemu git -vnc fails due to missing en-us keymap
Date: Mon, 14 Sep 2020 13:27:58 -0000 [thread overview]
Message-ID: <160009007915.15025.5721686079641285935.launchpad@gac.canonical.com> (raw)
In-Reply-To: 159978635021.22139.4037516560250644869.malonedeb@wampee.canonical.com
** Branch unlinked: lp:envbot/0.0.1
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1895219
Title:
qemu git -vnc fails due to missing en-us keymap
Status in QEMU:
New
Bug description:
If trying to run qemu with -vnc :0, it will fail with:
./qemu-system-x86_64 -vnc :2
qemu-system-x86_64: -vnc :2: could not read keymap file: 'en-us'
share/keymaps is missing en-us keymap and only has sl and sv,
confirmed previous stable versions had en-us.
Tried with multiple targets, on arm64 and amd64
Git commit hash: 9435a8b3dd35f1f926f1b9127e8a906217a5518a (head)
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1895219/+subscriptions
next prev parent reply other threads:[~2020-09-14 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 1:05 [Bug 1895219] [NEW] qemu git -vnc fails due to missing en-us keymap Darren Blaber
2020-09-12 12:18 ` [Bug 1895219] " Darren Blaber
2020-09-14 12:58 ` Darren Blaber
2020-09-14 13:27 ` Darren Blaber [this message]
2020-09-14 15:09 ` Alexander Bulekov
2020-09-14 15:09 ` Alexander Bulekov
2020-10-08 15:57 ` Alex Bennée
2021-04-09 2:45 ` hippieshaker
2021-05-08 6:04 ` Thomas Huth
2021-07-08 4:17 ` Launchpad Bug Tracker
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=160009007915.15025.5721686079641285935.launchpad@gac.canonical.com \
--to=1895219@bugs.launchpad.net \
--cc=qemu-devel@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).