https://bugzilla.suse.com/show_bug.cgi?id=1176302 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |1174720 -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c1 Stefan Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sbrabec@suse.com, | |schubi@suse.com Flags| |needinfo?(sbrabec@suse.com) --- Comment #1 from Stefan Schubert --- (In reply to Stanislav Brabec from comment #0)

In past, kbd had its own keymaps with different names and layouts than xkb.

Several years ago we generated a set of new keymaps based on xkb keymaps, and moved old ones to the kbd-legacy sub-package.

But these keymaps are still not used by default.

To fix this situation, we have to:

1. Change YaST keymap selection. kbd keymap should have the same name as xkb keymap.

Could you please give us some examples in order to see where it should be done ? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c3 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |sndirsch@suse.com --- Comment #3 from Stanislav Brabec --- Regarding 2a: There is already a patch for it: kbd-1.15.5-loadkeys-search-path.patch from Stefan Dirsch. But it does not work as expected: static const char *const dirpath1[] = { "", DATADIR "/" KEYMAPDIR "/**", DATADIR "/" XKBKEYMAPDIR "/", DATADIR "/" LEGACYKEYMAPDIR "/**", KERNDIR "/", 0 }; ... #define KEYMAPDIR "keymaps" #define XKBKEYMAPDIR "keymaps/xkb" #define LEGACYKEYMAPDIR "keymaps/legacy" => First, any directory in keymapdir is searched, then xkb dir, then legacy => The result is undefined. 2a is fixed: https://build.opensuse.org/request/show/835238 2b is not needed to implement. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c5 --- Comment #5 from Stanislav Brabec --- Stefan Dirsch: I guess that you did the whole xkb to kbd keymap generation. The search path was just a minor part of this work. Until now, we were using legacy keyboards by default, so the current behavior was OK. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c7 --- Comment #7 from Stanislav Brabec --- I would like to prepare a migration script for kbd, but I don't know the mechanism of assigning the locale default keymap in X. Could you give me a hint? Is it done by YaST during installation, by a display manager or by GNOME/KDE? -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c8 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@suse.com Flags| |needinfo?(sbrabec@suse.com) --- Comment #8 from Martin Vidner ---

the mechanism of assigning the locale default keymap in X

I'm not sure what you mean. Can you explain a bit, with an example? Also note that YaST internally uses some of the legacy keyboard names, which bleed over to systemd.rpm: /usr/share/systemd/kbd-model-map built from kbd-model-map.legacy -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 Stanislav Brabec changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|1174720 | -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1176302 https://bugzilla.suse.com/show_bug.cgi?id=1176302#c12 --- Comment #12 from Stefan Hundhammer --- See also https://github.com/yast/yast-country/pull/288 -- You are receiving this mail because: You are on the CC list for the bug.