Bugzilla – Bug 1087555
Configuring keyboard using Yast2 to use a German Keyboard with deadkeys for console and KDE doesn´t survive a reboot
Last modified: 2018-08-16 08:58:53 UTC
While I was exploring the bug report https://bugzilla.opensuse.org/show_bug.cgi?id=1055834 I figured out that Yast Keyboard Configuration does not handle the German keyboard settings properly.
I'm working on a Asus ROG Gaming Laptop with an external keyboard from Corsair K95 RGB. I need constantly grave and other accents so I would like to configure German deadkeys using Yast Keyboard module. This setting is only working in KDE and console for the actual session. After a reboot the layout is back to German nodeadkeys.
I investigated this issue and found that even if I manually setting up the system using localectl followed by a mkinitrd the settings are not saved.
This is what /etc/sysconfig/keyboard looks like after changing the keyboard:
## Path: Hardware/Keyboard
## Description: Keyboard settings for the text console
## Type: integer
## ServiceRestart: kbdsettings
# Keyboard delay time in ms (250, 500, 750, 1000)
## Type: string(2.0,2.1,2.3,2.5,2.7,3.0,3.3,3.7,4.0,4.3,4.6,5.0,5.5,6.0,6.7,7.5,8.0,8.6,9.2,10.0,10.9,12.0,13.3,15.0,16.0,17.1,18.5,20.0,21.8,24.0,26.7,30.0)
# Keyboard repeat rate (2.0 - 30.0)
## Type: list(bios,yes,no)
## Default: bios
# NumLock on? ("yes" or "no" or empty or "bios" for BIOS setting)
# This setting may interfere with GNOME /desktop/gnome/peripherals/keyboard/remember_numlock_state GConf key.
## Type: yesno
## Default: no
# ScrollLock on? ("yes" or "no")
## Type: yesno
## Default: no
# CapsLock on? ("yes" or "no")
## Type: yesno
## Default: no
# Disable CAPS LOCK and make it a normal Shift key?
# (Ctrl Caps Lock will still toggle Caps Lock functionality)
# Note that you need to tweak the xkb maps or use xmodmap
# if you want to do the same under X-Windows. In ~/.Xmodmap:
# keycode 0x42 = Shift_L Shift_L
## Type: string
# ttys for the above settings
# Example: "tty1 tty2"
# "" for tty's 1-6
# The YaST-internal identifier of the attached keyboard.
This is what I setup manually:
localectl --no-convert set-locale de-latin1
localectl --no-convert set-x11-keymap de-latin1 pc104 de terminate:ctrl_alt_bksp
But t his is a localectl issue, then.
I'm not familiar how Yast Keyboard settings aqre configured. Probably it use localectl as well, probably it does it's own thing. And if localectl is used my way (config+mkinitrd) it should result in a working configuration which also survives a reboot. Actually it simply does not work.
So, saying it's a localectl issue then is not really helpful and indicates me that you don't wnat spend time on this.
Am I correct?
Could you show the content of /etc/vconsole.conf ?
(In reply to Alexander Nolting from comment #0)
> This is what I setup manually:
> localectl --no-convert set-locale de-latin1
> localectl --no-convert set-x11-keymap de-latin1 pc104 de
These 2 commands are not supposed to configure the keyboard layout used by the virtual consoles.
here the output from /etc/vconsole
anolting@localhost:~> cat /etc/vconsole.conf
Please note, that I don´t want to setup specific settings in KDE use Systemsettings. In my opinion seetting up the keyboard in YasT should be enough for both WM/DE and console (vconsole/tty)
by the way: before I opened this ticket, I investigated into the vconsole service not starting issue (can be found here: Bug 1055834 [FAILED] Failed to start Setup Virtual Console - https://bugzilla.opensuse.org/show_bug.cgi?id=1055834) as I´m having the same issue.
And after aas I digged into this I learned that systemd-vconsole-setup.service, systemd-vconsole-setup is invoked by systemd-localed.service, systemd-localed after setting up the system locale settings, as well as the console key mapping and default X11 key mapping using localectl.
I probably missed some configuration for vconsole but I´m prety sure if you use systemd/localed then thats the way to configure the system locale and keyboard settings.
Please correct me and point to the right documentation if I´m wrong.
It looks like that I have missed to set up the keymap using
localectl set-keymap --no-covnert keymap LANG=de_DE.utf8
followed by a mkinitrd.
Now I have a working vconsole. But KDE is still using nodeadkeys.
I used both XkbVariant=de and XkbVarain=basic.
Here my /etc/X11.xorg.conf.d/00-keyboard.conf:
localhost:/home/anolting # cat /etc/X11/xorg.conf.d/00-keyboard.conf
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# instruct systemd-localed to update it.
Option "XkbLayout" "de-latin1"
Option "XkbModel" "pc104"
Option "XkbVariant" "de"
(In reply to Alexander Nolting from comment #6)
> I probably missed some configuration for vconsole but I´m prety sure if you
> use systemd/localed then thats the way to configure the system locale and
> keyboard settings.
That's correct, however please note that the system-wide settings are used by systemd and every services it starts.
But these can be overridden by the DE once the user logs in.
(In reply to Alexander Nolting from comment #7)
> Now I have a working vconsole.
> But KDE is still using nodeadkeys.
> I used both XkbVariant=de and XkbVarain=basic.
> Here my /etc/X11.xorg.conf.d/00-keyboard.conf:
> localhost:/home/anolting # cat /etc/X11/xorg.conf.d/00-keyboard.conf
> # Written by systemd-localed(8), read by systemd-localed and Xorg. It's
> # probably wise not to edit this file manually. Use localectl(1) to
> # instruct systemd-localed to update it.
> Section "InputClass"
> Identifier "system-keyboard"
> MatchIsKeyboard "on"
> Option "XkbLayout" "de-latin1"
> Option "XkbModel" "pc104"
> Option "XkbVariant" "de"
The content of /etc/X11/xorg.conf.d/00-keyboard.conf looks correct, so it's probably overridden (or ignored) by your DE once you log in.
As far as systemd is concerned, it seems that everything is OK.
I don't know if yast is supposed to also manage the settings used by the DE, I'm re-assigning this back to Steffen Winterfeldt in the hope that he'll clarify this.
the answers are not really satisfying me for several reasons:
1. You missed the issue which caused to open this bug report: the Yast2 Keyboard Module is not working properly. It does not manipulate the reuqired files properly.
2. MY DE is packaged and maintained by SuSE. If KDE is not configuring my Keyboard the way I want to have it configured in Yast2 and also not if I manually configure it using localectl, then there might be another issue found. It seems to me as the movement to localed requires more QA and testing.
3. It is (at the moment) not documented if and if so, how to configure locales system wide using any other option than Yast2. This includes also a lack of documentation of how SuSE has integrated systemd/localed/networkd etc... -> files used, tools used, configuration options supported and so on.
4. I still does not know (and it seems also not documented in SDB) from and to which location KDE does read/write it´s keyboard settings. I personally does all the home admin work for laptops of my family and I really appreciate the idea of having a configuration system like Yast as this much more clean and easier to use compared to KDE's systemsettings.
Can you please help me with that issues?
(In reply to Alexander Nolting from comment #10)
> Hello Franck,
> the answers are not really satisfying me for several reasons:
Just to make it clear, I didn't say that there's no issue here, I just said that as far as systemd is concerned, every things look OK and the settings used by the system are updated correctly (both /etc/vconsole.conf and /etc/X11/xorg.conf.d/00-keyboard.conf).
To make it clear, the system settings are the ones used by PID1 and all services it spawns (for example it includes the locale used by all daemons to log messages in the journal).
Again if your DM/DE chooses to override these settings because you explicitly configure them through some menus then the behavior you're seeing is expected I would say.
However if you haven't done any changes in your DM/DE settings, then that probably means that they *always* overwrite the default (system) settings which might be your problem (especially if the settings are not taking effects after a reboot).
But currently I don't see any prob in neither systemd nor yast2, unless the yast2 is supposed to configure the settings of all supported DE, but I doubt it.
(In reply to Franck Bui from comment #11)
> (In reply to Alexander Nolting from comment #10)
> > Hello Franck,
> > the answers are not really satisfying me for several reasons:
> Just to make it clear, I didn't say that there's no issue here, I just said
> that as far as systemd is concerned, every things look OK and the settings
> used by the system are updated correctly (both /etc/vconsole.conf and
> To make it clear, the system settings are the ones used by PID1 and all
> services it spawns (for example it includes the locale used by all daemons
> to log messages in the journal).
> Again if your DM/DE chooses to override these settings because you
> explicitly configure them through some menus then the behavior you're seeing
> is expected I would say.
> However if you haven't done any changes in your DM/DE settings, then that
> probably means that they *always* overwrite the default (system) settings
> which might be your problem (especially if the settings are not taking
> effects after a reboot).
> But currently I don't see any prob in neither systemd nor yast2, unless the
> yast2 is supposed to configure the settings of all supported DE, but I doubt
let me clarify also something:
I said all the time I want to have set my locales and Keyboard settings system-wide using Yast2. I mentioned also that I don't want and have configured KDE keyboard and locale behavior using KDE's systemsettings.
I have never said that systemd, localed has a problem. I said and mentioned that I've got vconsole managed by localed the way I want to have it, but I said also that YaST2 keyboard module wont do this job properly.
I also said that I don't know much about the internals of Yast and this includes also the answer to the question (at least you came also to this conclusion) if YaST is intended to setup the locales and keyboard behavior system-wide. And system-wide includes IMHO also the setup for any DE.
And last all the information about localectl I played with and the results I got were only to help you to figure out what may go wrong with Yast. I'm not here to blame you or any other working on this ticket. But IMHO support is not only to help the customer - one of its main function is to figure out if there is are misunderstanding or interpretation of how a product is designed and should work.
So if you cant answer this question and also not Steffen, please forward this issue to the appropriate person or group which is able to determine what the purpose and targets of YaST are.
Please also note that KDE sometimes also does keyboard remapping on top of what the system does; there is a KDE applet where you can switch between different keyboard layouts, including activating/deactivating the deadkeys. Please also check if this is possibly active and maybe overrides the system settings.
(In reply to Stefan Hundhammer from comment #13)
> Please also note that KDE sometimes also does keyboard remapping on top of
> what the system does; there is a KDE applet where you can switch between
> different keyboard layouts, including activating/deactivating the deadkeys.
> Please also check if this is possibly active and maybe overrides the system
I know this. But this is not the question or the case here and if so, then it may be another issue.
In this specific case we are at a point where we had figured out that it is important to make clear what YaST will provide. Afterwards we can get back to the originally problem report and decide if this is a bug, there is lack of documentation or there is some misunderstanding.
The starting point for all keyboard configs is /etc/vconsole.conf.
So, can you run yast's keyboard module, set the layout you'd like, and check /etc/vconsole.conf afterwards. Does it have the correct content? *If not*, please attach yast logs.
To do this run 'save_y2logs' and attach the log file archive this command
Alex, any news on this? See questions in comment #15.
Still waiting for feedback (see comment #15)
no response more then month