Broken keymaps for brazilian keyboards in kbd-bkeymaps (edge repo)
After update in edge repo (2019-08-19 09:12:59) all brazilian keymaps were damaged.
All keys are out of order.
Activity
The kbd 2.2.0 upgrade also caused some issues for me: First of all enabling
terminus-fontusingsetfont ter-v16n.psf.gznow causes aBad input file sizewhile it used to work withkbd < 2.2.0. Callingsetfont ter-v16n.psfinstead (omitting the.gzextension works). However,/etc/init.d/consolefontmakes the assumption that consolefonts end with.gzif this no longer holds the init script needs to be adjusted. See: https://git.alpinelinux.org/aports/tree/main/openrc/0007-make-consolefont-service-compatible-with-busyboxs-se.patch#n63 Update: Absolute path with.gzextensions works as well.Additionally, loading the binary keymap in the initramfs failed for me resulting in a totally garbage keybinding. Not sure why this is the case, I need to investigate this further.
Edited by Sören Tempel-
Created in upstream bug for the former: https://github.com/legionus/kbd/issues/32
mentioned in commit 462dba8e
Additionally, loading the binary keymap in the initramfs failed for me resulting in a totally garbage keybinding. Not sure why this is the case, I need to investigate this further.
How is the status on this? I just upgraded a system to edge (kbd 2.2.0-r1 is installed) and the keymap is garbage now, completely random. ALT is actually ENTER etc. I tried de-de and us-us via setup-keymap, even ran mkinitfs and it is all the same. Came accross https://github.com/legionus/kbd/commit/c994c7763b390d28ac92223eaa6176a136ad7b58 but have not tested it, maybe this one also needs to be backported?
-
Yes, that definitely needs to be backported. I committed a backport in 81189e08 this should fix the problem outlined by the OP.
mentioned in commit 81189e08
