I've pushed a commit to fix cloud-init's PR 4361 to ensure we write /etc/default/keyboard correctly instead of calling localectl set-x11-keymap directly.
This proposed changeset is small enough that cloud-init user-data can actually modify itself on disk before cc_keyboard runs using write_files directives.
@DaveJones,
I've attached test_write_etc_default_keyboard.yaml which is cloud-config user-data that will leverage the proposal in PR #4361.
Would you be able to launch daily mantic arm64 images on raspi with the following user-data test_write_etc_default_keyboard.yaml to confirm the proposed cloud-init fixes from PR 4361 properly set the keymap/layout for you?
Once we validate that behavior on Focal, Jammy and Lunar doesn't degrade, we will include this in 23.3 release (tomorrow/Monday) and SRU it into Focal/Jammy and Lunar.
I've pushed a commit to fix cloud-init's PR 4361 to ensure we write /etc/default/ keyboard correctly instead of calling localectl set-x11-keymap directly.
I have also published preliminary 23.3 cloud-init deb packages for both Jammy and Mantic to https:/ /launchpad. net/~chad. smith/+ archive/ ubuntu/ cloud-init- uploads that can be used to validate that writing /etc/default/ keyboard directly works as advertised
This proposed changeset is small enough that cloud-init user-data can actually modify itself on disk before cc_keyboard runs using write_files directives.
@DaveJones,
I've attached test_write_ etc_default_ keyboard. yaml which is cloud-config user-data that will leverage the proposal in PR #4361.
Would you be able to launch daily mantic arm64 images on raspi with the following user-data test_write_ etc_default_ keyboard. yaml to confirm the proposed cloud-init fixes from PR 4361 properly set the keymap/layout for you?
Once we validate that behavior on Focal, Jammy and Lunar doesn't degrade, we will include this in 23.3 release (tomorrow/Monday) and SRU it into Focal/Jammy and Lunar.