Release Engineering

Tasklist

FS#72464 - [releng] Add libxkbcommon to the installation medium

Attached to Project: Release Engineering
Opened by Managor (Managor) - Monday, 18 October 2021, 17:07 GMT
Last edited by David Runge (dvzrv) - Thursday, 21 October 2021, 10:42 GMT
Task Type Feature Request
Category ArchISO
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Without libxkbcommon, I can not set the x11 keyboard with `localectl set-x11-keymap fi`. It gives me an error `Failed to set keymap: Local keyboard configuration not supported on this system.`
This task depends upon

Closed by  David Runge (dvzrv)
Thursday, 21 October 2021, 10:42 GMT
Reason for closing:  Not a bug
Additional comments about closing:  For installation related questions please refer to the wiki or ask on the relevant mailing lists/ forums/ IRC channels.
Comment by David Runge (dvzrv) - Wednesday, 20 October 2021, 11:20 GMT
@Managor: Thanks for the ticket.

Can you be more specific about in which exact environment you are trying to run localectl? In the environment archiso boots into or in a arch-chroot during installation?

Why does `loadkeys` [1] not suffice?

[1] https://wiki.archlinux.org/title/Installation_guide#Set_the_console_keyboard_layout
Comment by Managor (Managor) - Wednesday, 20 October 2021, 15:06 GMT
I'm trying to run it in the arch-chroot environment.

The reason why loadkeys doesn't suffice is because I'm trying to automate as much as possible in my install script all the way to the desktop environment.

But sadly now that I've tested it around, the setting doesn't seem to persist similar to how `timedatectl set-ntp true` doesn't persist

This issue can probably be closed.

As a side note, do you have any hints on how to automate those through the installation medium?
Comment by David Runge (dvzrv) - Thursday, 21 October 2021, 10:41 GMT
You could rely on provisioning /etc/locale.conf and /etc/vconsole.conf in the to-be-installed system[.

That can be achieved e.g. by using ansible. I'm not sure whether localectl can deal well with being run in a chroot.

At any rate, as pointed out by yourself, this is not an issue with the installation medium, but with however the system is installed using it. :)

Loading...