[debbugs-tracker] bug#25453: closed (Inconsistent keyboard layout affecting encrypted root)

[GNU bug Tracking System]

Your message dated Sun, 24 Mar 2019 23:21:10 +0100
with message-id <address@hidden>
and subject line Re: bug#25453: Inconsistent keyboard layout affecting 
encrypted root
has caused the debbugs.gnu.org bug report #25453,
regarding Inconsistent keyboard layout affecting encrypted root
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25453: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25453
GNU Bug Tracking System
Contact address@hidden with problems

--- Begin Message --- Subject: Inconsistent keyboard layout affecting encrypted root Date: Sun, 15 Jan 2017 06:55:24 +0000

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.

The ideal behaviour here is that the way in which the passphrase is set
in the installer is the way in which it has to be entered into Grub and
during the early boot of the system. 

signature.asc
Description: PGP signature

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#25453: Inconsistent keyboard layout affecting encrypted root
>
>
>
>
> Date: 
>
> Sun, 24 Mar 2019 23:21:10 +0100
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
>
>
>
>
> Hi Chris!
>
> address@hidden (Ludovic Courtès) skribis:
>
> > Christopher Baines <address@hidden> 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.
>
> Ludo’.
>
>
> --- End Message ---