Activity log for bug #1954575

Date Who What changed Old value New value Message
2021-12-11 23:21:36 Flauschie bug added bug
2021-12-11 23:22:43 Flauschie description I think the manual and autoinstall methods of Ubuntu Server 20.04.3 got a bug regarding the keyboard / keymap setup. This is not (or maybe could be) related to the setup where the configured keyboard layout gets forgotten throughout the different setup screens. I am installing with a specified keyboard layout but it won't get recognized until the system fully booted (aka login screen). So in console or in my case the decryption phase I cannot properly enter my secret. I think it switches back tot he default en_US. I tried calling `update-initramfs -u` in target (and directly, too) during the late-commands phase on an autoinstall but it doesn't change anything. It will only work calling it once the system booted and I'm logged in. After being regenerated I have the proper keymap for the decryption. This also happens for a manual install using the live server 20.04.3 image right from source. I define the keyboard / locale in the appropriate section and it doesn't apply until the system booted. I can reproduce this in 10/10 cases using the manual install and autoinstall method. checked: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bugs?orderby=importance&start=0 I think the manual and autoinstall methods of Ubuntu Server 20.04.3 got a bug regarding the keyboard / keymap setup. This is not (or maybe could be) related to the setup where the configured keyboard layout gets forgotten throughout the different setup screens. I am installing with a specified keyboard layout but it won't get recognized until the system fully booted (aka login screen). So in console or in my case the decryption phase I cannot properly enter my secret. I think it switches back to the default en_US. I tried calling `update-initramfs -u` in target (and directly, too) during the late-commands phase on an autoinstall but it doesn't change anything. It will only work calling it once the system booted and I'm logged in. After being regenerated I have the proper keymap for the decryption. This also happens for a manual install using the live server 20.04.3 image right from source. I define the keyboard / locale in the appropriate section and it doesn't apply until the system booted. I can reproduce this in 10/10 cases using the manual install and autoinstall method. checked: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bugs?orderby=importance&start=0
2021-12-12 00:24:58 Ubuntu Foundations Team Bug Bot tags bot-comment
2021-12-12 15:05:00 Paul White tags bot-comment bot-comment focal
2021-12-12 15:05:15 Paul White affects ubuntu subiquity (Ubuntu)
2021-12-13 17:53:47 Brian Murray bug task added subiquity
2021-12-16 00:20:54 Flauschie description I think the manual and autoinstall methods of Ubuntu Server 20.04.3 got a bug regarding the keyboard / keymap setup. This is not (or maybe could be) related to the setup where the configured keyboard layout gets forgotten throughout the different setup screens. I am installing with a specified keyboard layout but it won't get recognized until the system fully booted (aka login screen). So in console or in my case the decryption phase I cannot properly enter my secret. I think it switches back to the default en_US. I tried calling `update-initramfs -u` in target (and directly, too) during the late-commands phase on an autoinstall but it doesn't change anything. It will only work calling it once the system booted and I'm logged in. After being regenerated I have the proper keymap for the decryption. This also happens for a manual install using the live server 20.04.3 image right from source. I define the keyboard / locale in the appropriate section and it doesn't apply until the system booted. I can reproduce this in 10/10 cases using the manual install and autoinstall method. checked: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bugs?orderby=importance&start=0 I think the manual and autoinstall methods of Ubuntu Server 20.04.3 got a bug regarding the keyboard / keymap setup. This is not (or maybe could be) related to the setup where the configured keyboard layout gets forgotten throughout the different setup screens. I am installing with a specified keyboard layout but it won't get recognized until the system fully booted (aka login screen). So in console or in my case the decryption phase I cannot properly enter my secret. I think it switches back to the default en_US. I tried calling `update-initramfs -u` in target (and directly, too) during the late-commands phase on an autoinstall but it doesn't change anything. It will only work calling it once the system booted and I'm logged in. After being regenerated I have the proper keymap for the decryption. This also happens for a manual install using the live server 20.04.3 image right from source. I define the keyboard / locale in the appropriate section and it doesn't apply until the system booted. I can reproduce this in 10/10 cases using the manual install and autoinstall method. checked: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bugs?orderby=importance&start=0 EDIT: And yes, probably cloud-init is responsible for it to be working on login. But this is simply too late. There is no excuse.
2022-02-18 18:12:50 Florian Lohoff bug added subscriber Florian Lohoff
2022-02-18 18:14:21 Launchpad Janitor subiquity (Ubuntu): status New Confirmed