From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#25453: Inconsistent keyboard layout affecting encrypted root Date: Sun, 24 Mar 2019 23:21:10 +0100 Message-ID: <87k1gnsyll.fsf@gnu.org> References: <87wpdwzuar.fsf@cbaines.net> <87vat9akzj.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:56567) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h8BVH-0002Fn-LK for bug-guix@gnu.org; Sun, 24 Mar 2019 18:22:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h8BVD-0006HH-AF for bug-guix@gnu.org; Sun, 24 Mar 2019 18:22:06 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:43709) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h8BVC-0006Gr-Mx for bug-guix@gnu.org; Sun, 24 Mar 2019 18:22:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1h8BVC-0005lr-I8 for bug-guix@gnu.org; Sun, 24 Mar 2019 18:22:02 -0400 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: In-Reply-To: <87vat9akzj.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 20 Jan 2017 15:01:36 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Christopher Baines Cc: 25453-done@debbugs.gnu.org Hi Chris! ludo@gnu.org (Ludovic Court=C3=A8s) skribis: > Christopher Baines 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 =E2=80=98console-k= eymap=E2=80=99 > Shepherd service, which invokes =E2=80=98loadkeys=E2=80=99. That happens= after > =E2=80=9Ccryptsetup --open=E2=80=9D 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=E2=80=99.