http://bugzilla.suse.com/show_bug.cgi?id=1124921 http://bugzilla.suse.com/show_bug.cgi?id=1124921#c22 --- Comment #22 from Ancor Gonzalez Sosa --- Thanks Stefan. That reduce the number of entries in no-clue-what-to-do status to five. All of them use a keymap for the "pc104" keyboard model that is only present in kbd-legacy without a clear equivalent in the xkb (i.e. non-legacy) directory. In all cases, for all other keyboard models ("macintosh", "type4", "type5" and "type5_euro") only "us" or "us-mac" is used. And all they correspond to languages that DO NOT use eutlatgr in the yast2-country consolefonts file. https://github.com/yast/yast-country/blob/master/console/src/data/consolefon... - Greek * map for "pc104": gr.map.gz * consolefonts: iso07u-16.psfu for both "el_GR" and "el_GR.UTF-8" - Russian * map for "pc104": ruwin_alt-UTF-8.map.gz * consolefonts: UniCyr_8x16.psf for "ru", "ru_RU.KOI8-R" and "ru_RU.UTF-8" - Serbian * map for "pc104": sr-cy.map.gz * consolefonts: - UniCyr_8x16.psf for "sr" and "sr_RS.UTF-8" - eurlatgr.psfu for "sr_RS@latin" -Tajik * map for "pc104": tj_alt-UTF8.map.gz * consolefonts: UniCyr_8x16.psf for both "tg" and "tg_TJ.UTF-8" - Ukranian * map for "pc104": ua-utf.map.gz * consolefonts: UniCyr_8x16.psf for both "uk" and "uk_UA.UTF-8" Maybe for Russian we could use "ru-cv_latin.map.gz" (the only map in the non-legacy directory that matches any of those five languages), but that would really be a shot in the dark. What I would do to leave the file in the best possible shape: - Step 1: fix keyboard_raw_opensuse.ycp * Fix the "us1", "ch-de-sundeadkeys" and "ch-fr-sundeadkeys" typos * Change "arabic" and "khmer" into "us" (they are links, after all) - Step 2: unify the files in openSUSE and SLE, using only the content of keyboard_raw_opensuse - Step 3: add a "legacy" flag to the file and implement a mechanism in YaST to ensure kbd-legacy is installed if a legacy keymap is selected (one of the above). I would do all that targeting SLE-15-SP2, in principle. I'm not sure whether trying to fix it via maintenance update for SLE-15-SP1 is worth it. -- You are receiving this mail because: You are on the CC list for the bug.