From 3a2c0bc2deb008ae5bdc1e1ca8affb67a0adaf57 Mon Sep 17 00:00:00 2001 From: Erwan Le Floch <90708860+erlefloch@users.noreply.github.com> Date: Mon, 17 Jul 2023 15:47:15 +0200 Subject: [PATCH] Add LUKS keyboard issue to the known limitations (#156) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Timothée Ravier --- modules/ROOT/pages/installation.adoc | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/modules/ROOT/pages/installation.adoc b/modules/ROOT/pages/installation.adoc index 14f2afe..a667325 100644 --- a/modules/ROOT/pages/installation.adoc +++ b/modules/ROOT/pages/installation.adoc @@ -23,6 +23,16 @@ If you are uncertain about this, {variant-name} can also be tested in a virtual It is possible to make {variant-name} work for both dual boot and manual partitioning, and some guidance is provided on manual partitioning below. However, there are hazards involved in both cases, and you should only attempt to use these features if you have done the necessary research, and are confident that you can overcome any issues that you might encounter. +*The keyboard layout selected during installation is not used for the LUKS unlock screen of {variant-name}.* + +Regardless of your selection during the installation process, the keyboard layout available for the LUKS unlock screen will default to `en-US` (English - United States of America). +You can workaround this issue by running the following command on the first boot after the installation: + `rpm-ostree initramfs-etc --track=/etc/vconsole.conf`. + +To avoid struggling when having to type the LUKS passphrase for the first time, you could set during installation a disk encryption passphrase that is easy to type with the `en-US` keyboard layout, and then change it to the passphrase that you actually want through the GNOME https://apps.gnome.org/en-GB/app/org.gnome.DiskUtility[Disks] app. + +See https://bugzilla.redhat.com/show_bug.cgi?id=1890085[bug #1890085] (Red Hat Bugzilla) and https://github.com/fedora-silverblue/issue-tracker/issues/3[issue #3] (Fedora Silverblue issue tracker) for details. + [[getting-silverblue]] == Getting {variant-name}