From: Christopher Baines <mail@cbaines.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 25453-done@debbugs.gnu.org
Subject: bug#25453: Inconsistent keyboard layout affecting encrypted root
Date: Mon, 25 Mar 2019 05:44:31 +0000 [thread overview]
Message-ID: <874l7rcxts.fsf@cbaines.net> (raw)
In-Reply-To: <87k1gnsyll.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi Chris!
>
> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> Christopher Baines <mail@cbaines.net> skribis:
>>
>>> I'm using a UK keyboard layout with a computer that I recently installed
>>> GuixSD on with a encrypted root parition. Immediately after installation
>>> when I attempted to boot in to the new system for the first time I had
>>> to enter the passphrase twice, and in doing this, first I had to use the
>>> keyboard layout under which I carried out the installation (the layout
>>> which I had intended to use), and then during the early boot stage of
>>> the system I had to enter the passphrase using a different keyboard
>>> layout.
>>
>> Currently installing a keymap is something done by the ‘console-keymap’
>> Shepherd service, which invokes ‘loadkeys’. That happens after
>> “cryptsetup --open” has opened your encrypted root device, hence the
>> problem.
>
> This is finally fixed by commit
> ae7a316b9da0d1a50c5abdc531c68c8e98e561c9, which initializes the console
> keyboard layout straight from the initrd.
Exciting, thanks Ludo :)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
prev parent reply other threads:[~2019-03-25 5:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-15 6:55 bug#25453: Inconsistent keyboard layout affecting encrypted root Christopher Baines
2017-01-20 14:01 ` Ludovic Courtès
2018-01-14 13:22 ` Mathieu Lirzin
2018-01-17 7:05 ` Chris Marusich
2018-01-17 8:29 ` ng0
2019-03-24 22:21 ` Ludovic Courtès
2019-03-25 5:44 ` Christopher Baines [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874l7rcxts.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=25453-done@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).