Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED]ERROR: keymaps failed to start (Read 2324 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

[SOLVED]ERROR: keymaps failed to start

Hi,

I have this error since i installed Artix and i don't know what to do here. What file does loadkeys load ?

My keyboard layout is Portuguese, my Artix is in English, exactly as instended but everytime i turn the laptop on i get to see this error and i would like to fix whatever is wrong with it. :|

----------------------------------------------------------------------------------
Artix-PC:[occlus]:/etc/conf.d$ sudo rc-service keymaps restart

keymaps           | * Setting keyboard mode [UTF-8] ...
keymaps           |The keyboard is in some unknown mode
keymaps           |Changing to the requested mode may make your keyboard unusable, please use -f to force the change.                                                               [ ok ]
keymaps           | * Loading key mappings [pt] ...
keymaps           |loadkeys: Unable to open file: pt: No such file or directory
keymaps           | * Error loading key mappings                                       [ !! ]
keymaps           | * ERROR: keymaps failed to start
----------------------------------------------------------------------------------

Artix-PC:[occlus]:/etc/conf.d$ cat /etc/vconsole.conf

KEYMAP=pt_PT.UTF-8
----------------------------------------------------------------------------------
Artix-PC:[occlus]:/etc/conf.d$ cat keymaps

# Use keymap to specify the default console keymap.  There is a complete tree
# of keymaps in /usr/share/keymaps to choose from.
keymap="pt"

# Should we first load the 'windowkeys' console keymap?  Most x86 users will
# say "yes" here.  Note that non-x86 users should leave it as "no".
# Loading this keymap will enable VT switching (like ALT+Left/Right)
# using the special windows keys on the linux console.
windowkeys="NO"

# The maps to load for extended keyboards.  Most users will leave this as is.
extended_keymaps=""
#extended_keymaps="backspace keypad euro2"

# Tell dumpkeys(1) to interpret character action codes to be
# from the specified character set.
# This only matters if you set unicode="yes" in /etc/rc.conf.
# For a list of valid sets, run `dumpkeys --help`
dumpkeys_charset=""

# Some fonts map AltGr-E to the currency symbol instead of the Euro.
# To fix this, set to "yes"
fix_euro="NO"
--------------------------------------------------------------------------

Technically everything works fine, do you know why i get this error and how to fix it ?

With thanks and regards,




Re: ERROR: keymaps failed to start

Reply #1
First of all, if you are using OpenRC, you don't need the /etc/vconsole.conf file. Second, pt_PT.UTF-8 is not a value for the KEYMAP variable, it's a value for LANG.

Third, and without further ado regarding your problem. There is no keymap called pt. You've been told about that by the loading script. Check the /usr/share/kbd/keymaps/i386/qwerty directory, there seems to be two available Portuguese keymaps, pt-latin1 and pt-latin9, choose one of them.

Re: ERROR: keymaps failed to start

Reply #2
Thank you Victor,

This was much time with systemd which caused bad habits, plus i'm now working professionally in a full microsoft environment and this had impact on my linux knowledge. It's unfortunate.

It's resolved,

Thank you for your help!

Re: [SOLVED]ERROR: keymaps failed to start

Reply #3
Just to add that /etc/vconsole.conf is sourced in 66 and s6 on startup (I didn't use runit and OpenRC much so IDK about them), but also I'd like to remind that /etc/vconsole.conf and loadkeys only affect ttys and don't affect X programs. For keyboard layout setting in X programs, you can use setxkbmap or X configuration files.

Re: [SOLVED]ERROR: keymaps failed to start

Reply #4
Just to add that /etc/vconsole.conf is sourced in 66 and s6 on startup (I didn't use runit and OpenRC much so IDK about them)
This file is used in Runit as well, but not in OpenRC, which has its own init scripts and corresponding configuration files.