http://bugzilla.opensuse.org/show_bug.cgi?id=1087555 http://bugzilla.opensuse.org/show_bug.cgi?id=1087555#c12 --- Comment #12 from Alexander Nolting --- (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 /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.

Hello Franck, 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. Best Alex -- You are receiving this mail because: You are on the CC list for the bug.