http://bugzilla.suse.com/show_bug.cgi?id=1166423 http://bugzilla.suse.com/show_bug.cgi?id=1166423#c17 Ancor Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ancor@suse.com) | --- Comment #17 from Ancor Gonzalez Sosa --- (In reply to Stanislav Brabec from comment #16)

Frank Kruger: Policy did not change, but some of legacy keymaps changed its name. But yast did not update names yet.

Now we have a bit problematic setup: YaST is now developed as a single code base for Tumbleweed, Leap and SLE, but kbd package has different versions with different names.

=> We need one of these solutions:

And I guess I'm in NEEDINFO because you want to read my opinion about them.

- migrate defaults to xkb based keymaps (preferred; it will allow to remove kbd-legacy from the default image)

That sounds good to me. Any clear downside?

- upgrade kbd in Leap&SLE

I don't think this is reasonable in the current stage of the upcoming Leap 15.2 and SLES-15-SP2. Many tests has been done already that would be kind of invalidated by such change.

- differentiate yast2-country defaults by product

This can be done, technically it's easy but I think it just moves the problem a bit forward in time, to the next SLE/Leap release. We would now have code/data in YaST for TW to manage kbd 2.2.0 and different code/data for Leap to manage 2.0.4. At some point, Leap will adopt 2.2.0 so we will unify the code/data again... just to maybe repeat the whole cycle in the future with another release of kdb. Sounds wrong to me. Unifying all this between SLE and openSUSE was IMO a good step for YaST and the distributions in general. Introducing now another divergence (between Leap and TW this time) looks, in my limited view, like a step backwards. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166423 http://bugzilla.suse.com/show_bug.cgi?id=1166423#c21 Karl Mistelberger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |karl.mistelberger@nefkom.ne | |t --- Comment #21 from Karl Mistelberger --- (In reply to Ludwig Nussel from comment #20)

Making yast write different keymaps is one part of the story. The other is that old names stay in vconsole.conf and the files where moved to a different directory where systemd-vconsole-setup doesn't find them. This move of directory was not done in upstream kbd, right? As such not surprising that systemd isn't prepared for that either. I doubt that the systemd maintainers want to carry yet another distro patch for this minor thing.

This is not a minor thing, but a big annoyance. The error causes long and pointless discussions. Just in case systemd doesn't get patched existing file should be added to initrd: /usr/share/kbd/keymaps/legacy/i386/qwertz/de-latin1-nodeadkeys.map.gz Current initrd has: usr/share/kbd usr/share/kbd/consolefonts usr/share/kbd/consolefonts/LatArCyrHeb-16.psfu usr/share/kbd/consolefonts/eurlatgr.psfu usr/share/kbd/keymaps usr/share/kbd/keymaps/xkb usr/share/kbd/keymaps/xkb/de-nodeadkeys.map -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166423 http://bugzilla.suse.com/show_bug.cgi?id=1166423#c23 --- Comment #23 from Karl Mistelberger ---

For the sake of curiosity, I have just copied 'de-latin1-nodeadkeys.map.gz' to /usr/share/kbd/keymaps/xkb/de-latin1-nodeadkeys.map.gz. After mkinitrd and a reboot vconsole does not start at all:

...

sudo systemctl status systemd-vconsole-setup.service systemd-vconsole-setup.service - Setup Virtual Console Loaded: loaded (/usr/lib/systemd/system/systemd-vconsole-setup.service; static; vendor preset: disabled) Active: failed (Result: exit-code) since Tue 2020-04-21 18:52:58 CEST; 8min ago Docs: man:systemd-vconsole-setup.service(8) man:vconsole.conf(5) Main PID: 944 (code=exited, status=1/FAILURE)

Apr 21 18:52:58 gropius systemd[1]: Starting Setup Virtual Console... Apr 21 18:52:58 gropius systemd-vconsole-setup[947]: syntax error, unexpected ERROR Apr 21 18:52:58 gropius systemd-vconsole-setup[944]: /usr/bin/loadkeys failed with exit status 1. Apr 21 18:52:58 gropius systemd[1]: systemd-vconsole-setup.service: Main process exited, code=exited, status=1/FAILURE Apr 21 18:52:58 gropius systemd[1]: systemd-vconsole-setup.service: Failed with result 'exit-code'. Apr 21 18:52:58 gropius systemd[1]: Failed to start Setup Virtual Console.

What do I miss?

Check initrd by running 'lsinitrd|grep usr/share/kbd'. Note: The file contains an include statement: erlangen:~ # zcat /usr/share/kbd/keymaps/legacy/i386/qwertz/de-latin1-nodeadkeys.map.gz # de-latin1-nodeadkeys.map: German keymap # Due to Olaf Flebbe (flebbe@pluto.tat.physik.uni-tuebingen.de) include "de-latin1.map" control keycode 7 = Control_asciicircum keycode 13 = apostrophe grave keycode 27 = plus asterisk asciitilde keycode 41 = asciicircum degree # corresponding keys in de-latin1.map: # keycode 13 = dead_acute dead_grave # keycode 27 = plus asterisk dead_tilde # keycode 41 = dead_circumflex degree erlangen:~ # You may need to do this by hand before copying. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166423 http://bugzilla.suse.com/show_bug.cgi?id=1166423#c25 --- Comment #25 from Karl Mistelberger --- (In reply to Frank Kruger from comment #24)

Thanks for the hint. There are indeed several "include" to be taken into account. This "Failed to start Setup Virtual Console" is like Groundhog Day.

It makes no sense. I looked up Fedora 31: KEYMAP="de-nodeadkeys" FONT="eurlatgr" vs. Tumbleweed: KEYMAP=de-latin1-nodeadkeys FONT=eurlatgr.psfu FONT_MAP= FONT_UNIMAP= So it should be feasible to fix systemd. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1166423 http://bugzilla.suse.com/show_bug.cgi?id=1166423#c27 --- Comment #27 from Karl Mistelberger --- (In reply to Frank Kruger from comment #26)

FYI: The revised kbd package from Ludwig Nussel's home repo (https://build.opensuse.org/package/show/ home%3Alnussel%3Abranches%3ABase%3ASystem/kbd) solves the issue for me. Thanks!

Needed 2 packages: erlangen:~ # zypper in kbd-2.2.0-163.1.x86_64 kbd-legacy-2.2.0-163.1.noarch Loading repository data... Reading installed packages... Resolving package dependencies... The following 2 packages are going to be upgraded: kbd kbd-legacy The following 2 packages are going to change vendor: kbd openSUSE -> obs://build.opensuse.org/home:lnussel:branches:Base:System kbd-legacy openSUSE -> obs://build.opensuse.org/home:lnussel:branches:Base:System https://build.opensuse.org/package/binaries/home:lnussel:branches:Base:Syste... -- You are receiving this mail because: You are on the CC list for the bug.