http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c1 --- Comment #1 from Marcus Meissner --- Created attachment 730600 --> http://bugzilla.suse.com/attachment.cgi?id=730600&action=edit /etc/sysconfig/language /etc/sysconfig/language -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c3 --- Comment #3 from Marcus Meissner --- Created attachment 730602 --> http://bugzilla.suse.com/attachment.cgi?id=730602&action=edit y2log-Z85vZ9.tar.xz yast2 logs -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c5 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |youpburden@gmail.com --- Comment #5 from Steffen Winterfeldt --- *** Bug 1047460 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c8 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kiyomi.kakitsubata@gmail.co | |m --- Comment #8 from Steffen Winterfeldt --- *** Bug 1048076 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c10 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gsouza@suse.com, | |igonzalezsosa@suse.com --- Comment #10 from Steffen Winterfeldt --- There are actually two things: (1)

/usr/bin/localectl --no-convert set-keymap de-nodeadkeys Failed to set keymap: Failed to execute program org.freedesktop.locale1: Permission denied

'man localectl' says:

It communicates with systemd-localed(8) to modify files such as /etc/locale.conf and /etc/vconsole.conf.

This sentence is new in TW. Note that we don't have systemd running during installation. (2) 'yast keyboard' fiddles with a non-existent 'kbd.service'. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c12 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(sndirsch@suse.com | |) | --- Comment #12 from Stefan Dirsch --- (In reply to Lukas Ocilka from comment #11)

The change was implemented as an answer to https://bugzilla.suse.com/show_bug.cgi?id=1023774

Stefan, what should we do then?

I have no idea. I guess for such issues we need to create a script during installation, which is executed the first time, when the system boots after installation with systemd active. And only then and only once. I know, this is crap, but you asked me for a proposal. ;-) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c14 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com --- Comment #14 from Thomas Blume --- (In reply to Egbert Eich from comment #13)

(In reply to Lukas Ocilka from comment #11)

...

The change was implemented as an answer to https://bugzilla.suse.com/show_bug.cgi?id=1023774

Stefan, what should we do then?

Wouldn't it make sense to request some input from the systemd experts about this?

I guess the answer it a fix for bug#1014991 (see bug 1014991 comment#7). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c16 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com Flags|needinfo?(systemd-maintaine | |rs@suse.de) | --- Comment #16 from Franck Bui --- Or maybe the installer (and only the installer) could initialize /etc/vconsole.conf directly ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c18 --- Comment #18 from Franck Bui --- Indeed but maybe we could make an exception during the *installation* process... Or maybe introduce something like "yast2-firstboot.service" as it was suggested by Thomas. That might be also needed for other stuff that YaST needs to run during the firstboot. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c20 --- Comment #20 from Franck Bui --- (In reply to Stefan Dirsch from comment #19)

No, everything would be in an inconsistent state again!

could you refresh my memory ? ;) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c22 --- Comment #22 from Lukas Ocilka --- There's one important thing: There is no second-stage installation *, so everything needs to be done before reboot. (* Well, there's an optional second-stage for AutoYaST) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c24 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(snwint@suse.com) | --- Comment #24 from Steffen Winterfeldt --- As Lukas wrote, there is no second stage any more; the system has to be configured properly when yast exists. Why would writing vconsole.conf be a problem? There's no localed running, so no confusion. Or not? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c26 --- Comment #26 from Lukas Ocilka --- OK, so we have basically two options: A. In the installer, write /etc/vconsole.conf directly, as there's no systemd running and thus we can't use it. B. Create yet another one-off systemd service (script) that would be called during the system boot and adjust all settings that can't be set during the initial installation. The service and the script would not be part of YaST but part of some separate package as no "YaST on the system" is a required feature. Moreover, it would have to be called before YaST.Firstboot, which actually allows adjusting the system via YaST UI and also before YaST.Second-Stage, which is optional for AutoYaST (and which can also change the system) Both options are somewhere between "the solution" and "a hack"... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c28 --- Comment #28 from Steffen Winterfeldt --- I've just tried and editing /etc/vconsole.conf and just rebooting sets the text console mapping correctly but X11 stays unchanged; apparently as nobody updates /etc/X11/xorg.conf.d/00-keyboard.conf. So I guess we'd have to write both files to be fine. [Option B seems a bit overkill to me.] -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c30 --- Comment #30 from Lukas Ocilka ---

From YaST POV, option C is the cleanest one.

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c32 --- Comment #32 from Thomas Blume --- (In reply to Franck Bui from comment #31)

Thomas could you open an issue (or a RFE) against upstream for requesting this new feature so we can hopefully see quickly if that would be the way to go ?

If we get a positive answer then we'll implement that.

Ok, done: https://github.com/systemd/systemd/issues/6346 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c34 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cfd_s12@web.de --- Comment #34 from Steffen Winterfeldt --- *** Bug 1032865 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c36 --- Comment #36 from P. Otato --- This bug is still unfixed. Although it is not hard to change the keyboard layout after the installation, it is a big handicap for Linux beginner and new Tumbleweed users since they won't be able to login due to this bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c43 --- Comment #43 from Sergio Lindo Mansilla --- It also happens selecting English language and German keyboard during installation. I get an installed system with English keyboard. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c49 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(thomas.blume@suse | |.com) | --- Comment #49 from Thomas Blume --- (In reply to Lukas Ocilka from comment #48)

There is a new comment at that issue: poettering commented 12 days ago sure, makes sense to add!

And I guess these are the changes (master might not be the correct branch): https://github.com/systemd/systemd/compare/master...tblume:add-keymap-setup- to-systemd-firstboot?expand=1

When can we expect this to be finished?

It's finished, I just wanted to test a bit more but I plan a pull request today.

I guess YaST depends on your implementation now? Thanks a lot! BTW :)

Yes, yast depends on it. I have some testpackages at: https://download.opensuse.org/repositories/home:/tsaupe:/branches:/openSUSE:... If you want to start the work on YaST you can use them. I still might change the code a bit if upstream requests some changes, but the functionality should stay the same. Just consult: /usr/bin/systemd-firstboot --help about how to set the keymap. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c51 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(thomas.blume@suse | |.com) --- Comment #51 from Lukas Ocilka --- Thomas, we need the package in SLE 15, otherwise we can't implement our side. What's the status? I don't see these changes there, but maybe I'm just looking at a wrong place... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c53 --- Comment #53 from Lukas Ocilka --- DUD is OK for testing, but Release Managers want that for Beta1. IMO we need a Plan B -> patch for systemd package. We'll plan for the YaST side of the implementation in less than 30 minutes, but we still depend on the new systemd to be there. We can implement it in in way that it's gonna silently fail... till the new package is in inst-sys. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c55 --- Comment #55 from Thomas Blume --- (In reply to Lukas Ocilka from comment #53)

DUD is OK for testing, but Release Managers want that for Beta1. IMO we need a Plan B -> patch for systemd package. We'll plan for the YaST side of the implementation in less than 30 minutes, but we still depend on the new systemd to be there.

We can implement it in in way that it's gonna silently fail... till the new package is in inst-sys.

With the patched systemd, the following works in the installation system: --> 0:g179:~ # systemd-firstboot --root /mnt --keymap=de-latin1-nodeadkeys Found container virtualization none. /mnt/etc/vconsole.conf written. 0:g179:~ # cat /mnt/etc/vconsole.conf KEYMAP=de-latin1-nodeadkeys --< -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c57 --- Comment #57 from Thomas Blume --- (In reply to Stefan Dirsch from comment #56)

Nice! And which content do we have in

/etc/X11/xorg.conf.d/00-keyboard.conf

afterwards?

I'm afraid that can't be done in the installation system. The command for conversion to X11 keymaps is done via dbus calls to localed. We know that this doesn't work in the installer. Furthermore, not every machine installs the Xserver. IMHO, that part should be done at first system boot by using the data from vsconsole.conf. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c60 --- Comment #60 from Steffen Winterfeldt --- See comment 56 and comment 57. The whole point here is that you should not write it directly as using systemd provides the additional benefit of syncing the various keymap definitions in the system. If this second part is not done, what's left? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c62 --- Comment #62 from Thomas Blume --- (In reply to Steffen Winterfeldt from comment #60)

See comment 56 and comment 57. The whole point here is that you should not write it directly as using systemd provides the additional benefit of syncing the various keymap definitions in the system. If this second part is not done, what's left?

This second part should be done via a service at initial system boot. I don't see any chance to do this without systemd running. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c64 --- Comment #64 from Josef Reidinger --- (In reply to Steffen Winterfeldt from comment #63)

When I tested this back then (comment 28) the x11 keymap config was not created on system startup. Does this work now, provided we have set /etc/vconsole.conf?

Well, I expect not, but I hope X should on first start set it from vconsole.conf ( not sure if it is doing it now, but it should start, as yast does not have second stage to do it ). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c66 --- Comment #66 from Stefan Dirsch --- See also comments #27 and #28. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c68 --- Comment #68 from Thomas Blume --- (In reply to Stefan Dirsch from comment #65)

X does read /etc/X11/xorg.conf.d/00-keyboard.conf. It does not write it! One needs to use localectl now for any keyboard configuration now in order to have a consistent state in Linux console and X11 keyboard setting and content of /etc/vconsole.conf.

What was writing /etc/X11/xorg.conf.d/00-keyboard.conf before systemd?

And running localectl in the installed system again with the same value, which has already been set in /etc/vconsole.conf during installation, will not create the X11 keybaord config file either. (localectl will think, it's already set, so nothing to do!).

That seems to be fixed in SLES15: --> g179:~ # cat /etc/os-release NAME="SLES" VERSION="15" VERSION_ID="15" PRETTY_NAME="SUSE Linux Enterprise Server 15" ID="sles" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15" g179:~ # g179:~ # cat /etc/X11/xorg.conf.d/00-keyboard.conf cat: /etc/X11/xorg.conf.d/00-keyboard.conf: No such file or directory g179:~ # g179:~ # g179:~ # cat /etc/vconsole.conf KEYMAP=de-latin1-nodeadkeys g179:~ # g179:~ # man localectl g179:~ # localectl set-x11-keymap de-latin1-nodeadkeys g179:~ # g179:~ # 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-nodeadkeys" EndSection g179:~ # --> -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c69 --- Comment #69 from Stefan Dirsch --- xdm.changes: ------------------------------------------------------------------- Wed Oct 18 15:01:24 UTC 2017 - sndirsch@suse.com - reintroduced /etc/X11/xdm/keytable script and the hook-up in /usr/lib/X11/display-manager to setup X11 keymaps, since YaST is not able to use localectl already during installation due to dbus and appropriate systemd services not running :-( (bsc#1046436) https://build.opensuse.org/request/show/534975 Unfortunately this change sits on top of another radical change in xdm package. ------------------------------------------------------------------- Thu Oct 12 10:08:28 UTC 2017 - dimstar@opensuse.org - Have update-alternatives handle Xinit's integration of the displaymanager, replacing /etc/sysconfig/displaymanager. - Add a dummy entry for 'console' - which is special-cased in the display-manager script to 'exit early'. In order for it to become an option for update-alternatives, the target needs to exist. - Update /usr/lib/X11/display-manager to get the default-displaymanager from the update-alternative setting instead of reading it from /etc/sysconfig/displaymanager. - Remove DISPLAYMANAGER from displaymanager.sysconfig template. - Add xdm-with-update-alternative.patch so the needed changes can be applied for suse_version >= 1330 only, not breaking Leap 42.x. - All that together solves boo#1053863. And that change depends on other displaymanager packages being adjusted first. This is going to become a funny week. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c73 --- Comment #73 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #70)

But anyway, feel free to give it a try. Built packages are in

obs://X11:XOrg/xdm

Meanwhile I gave it a try myself on Tumbleweed with xdm. Appears to work. (I've created manually /etc/vconsole.conf and then ran rcxdm restart. X11 keyboard layout has been created accordingly.) Unfortunately I can't test with other DMs like gdm, since they haven't been adjusted let alone checked in yet. :-( See https://build.opensuse.org/request/show/534162 for more details. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c75 --- Comment #75 from Frederic Crozat --- (In reply to Thomas Blume from comment #62)

(In reply to Steffen Winterfeldt from comment #60)

...

See comment 56 and comment 57. The whole point here is that you should not write it directly as using systemd provides the additional benefit of syncing the various keymap definitions in the system. If this second part is not done, what's left?

This second part should be done via a service at initial system boot. I don't see any chance to do this without systemd running.

If we don't do it as install time, we are loosing information from the install. Currently, it tries to call localectl set-x11-keymap with all parameters (layout model variant and options) Just relying on calling at runtime localectl set-keymap will just set the "default" computed by the kbd-model-map, which is not enough. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c77 --- Comment #77 from Stefan Dirsch --- I would call the issue fixed with my change in xdm package. BTW, running localectl set-x11-keymap $KEYMAP is simply wrong. You need to run localectl set-keymap $KEYMAP which sets the Linux console keyboard layout *and* writes the *appropriate* X11 keyboard layout (there is a mapping, which is needed!). Unfortunately it does not create /etc/X11/xorg.conf.d/00-keyboard.conf if it does not exist yet. Therefore I run localectl set-x11-keymap us in my script as workaround before if needed. Unfortunately this bug has never been fixed. Sigh. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c80 --- Comment #80 from Frederic Crozat --- (In reply to Stefan Dirsch from comment #79)

(In reply to Frederic Crozat from comment #75)

...

If we don't do it as install time, we are loosing information from the install. Currently, it tries to call localectl set-x11-keymap with all parameters (layout model variant and options)

Just relying on calling at runtime localectl set-keymap will just set the "default" computed by the kbd-model-map, which is not enough.

Frederic, console keyboard mappings are now generated from the X11 keyboard layouts with layout, mode, variant and options. Therefore they now have strange names like "de-latin1-nodeadkeys". This name is used in /etc/vconsole.conf. Therefore one just needs to run

localectl set-keymap <this-possibly-strange-name>

It then gets written to /etc/vconsole.conf, Linux console keyboard is set and X11 keybaord config snippet written.

Looks at yast2 code (yast-country to be precise), it is still calling: "/usr/bin/localectl --no-convert set-x11-keymap #{args.join(' ')}" and will try to set the various options for X11 (not sure where it will get the data from). If we don't expose those options in YaST nor the installer anymore, that's fine, but yast2-country might still need some cleanup -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c84 --- Comment #84 from Ladislav Slezák --- Um, no idea, that was used already before. Anyway that part is relevant only for the installed system, during installation Stage.initial == true. Let's focus on the installation here, at least for now... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c86 --- Comment #86 from Ladislav Slezák --- The YaST fix (https://github.com/yast/yast-country/pull/145) has been merged, submitted in yast2-country-4.0.3 in https://build.suse.de/request/show/144417 Unfortunately the problem was still not fix in my manual test. The /etc/vconsole.conf file was completely missing. I have used Build174.3 from http://download.suse.de/ibs/SUSE:/SLE-15:/GA:/Staging:/Y/images/iso/. Maybe it was not recent enough, there is some newer already. However, the YaST part worked as expected, the YaST log contains this line: modules/Keyboard.rb:895 Making console keyboard persistent: /usr/bin/systemd-firstboot --root /mnt --keymap 'cz-lat2-us' Which indicated that the correct command was call, also there is no error reported in the log so it succeeded. So for me the YaST side looks OK. Thomas or Stefan, please check it when the fixed YaST package is accepted. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c88 --- Comment #88 from Ladislav Slezák --- And also to reduce the risk of breaking something else in the Beta1 I'd rather postpone that fix after the release (if release managers are fine with that). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c91 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak@suse.com) | --- Comment #91 from Ladislav Slezák --- (In reply to Thomas Blume from comment #89)

...

I have used Build174.3 from http://download.suse.de/ibs/SUSE:/SLE-15:/GA:/Staging:/Y/images/iso/. Maybe it was not recent enough, there is some newer already.

I did a try with this image and cannot find the above call to systemd-firstboot in the yast logs. I which logfile have you seen it?

I used that build + manually patched Keyboard.rb YaST file. It wont work in the original build. The yast2-country-4.0.3 has been accepted to Staging Y, you just have to wait until the ISO is rebuilt. You can verify the package version by running "grep yast2-country /.packages.root" in the running inst-sys. (Either switch to another console or boot with "start_shell=1".) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c93 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(lslezak@suse.com) | --- Comment #93 from Ladislav Slezák --- 1. Boot with "startshell=1 netsetup=dhcp" 2. When the shell is active replace the Keyboard.rb file: a) copy this file to /tmp: https://github.com/yast/yast-country/blob/kbd_debug/keyboard/src/modules/Key... b) mount --bind /tmp/Keyboard.rb /usr/share/YaST2/modules/Keyboard.rb 3. Start the installation with "yast" 4. YaST displays a Popup after running the "systemd-firstboot" command with the result, keep the popup open 5. For debugging switch to another console (e.g. Ctrl+F2) or use Ctrl+Shift+Alt+X in YaST to open an xterm window (GUI only) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c100 --- Comment #100 from Ladislav Slezák --- OK, the fix will be submitted in few minutes... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c104 Ladislav Slezák changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #104 from Ladislav Slezák --- I have tested Build321.4 and the /etc/vconsole.conf file was created properly and the keyboard worked as expected in the console. Closing as FIXED. (Please test also the X installation, I did only minimal text mode test.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c106 --- Comment #106 from Frederic Crozat --- (In reply to Ladislav Slezák from comment #104)

I have tested Build321.4 and the /etc/vconsole.conf file was created properly and the keyboard worked as expected in the console.

Closing as FIXED.

(Please test also the X installation, I did only minimal text mode test.)

X installation works fine too, keymap is properly configured -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c108 --- Comment #108 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #83)

(In reply to Martin Vidner from comment #82)

...

FYI, the yast2-country part is (still not submitted) https://github.com/yast/yast-country/pull/145

May I ask, why you're using --no-convert localectl option. It is my understanding, that it won't create X11 keyboard configuration or in a wrong way.

(In reply to Ladislav Slezák from comment #84)

Um, no idea, that was used already before. Anyway that part is relevant only for the installed system, during installation Stage.initial == true. Let's focus on the installation here, at least for now...

So this issue has been successfully ignored, right? It basically means that keyboard layout changes via YaST after installation will only affect Linux console, but not X11. So we need an additional bug report for this? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c110 --- Comment #110 from Stefan Dirsch --- I cannot confirm this issue would have been fixed with the latest image. I've used /mounts/dist/install/SLE-15-Installer-TEST/SLE-15-Installer-DVD-x86_64-Build321.5-Media1.iso I've installed SLED with all available modules enabled. Registration key from https://wiki.microfocus.net/index.php?title=YAST/reg_codes ("real" SCC) I couldn't test SLES, since the key from this page didn't work, only the one for SLED did. I've selected packages as much as possible, as long as it could be resolved. Result was # cat /etc/vconsole.conf KEYMAP=de-latin1-nodeadkeys And no /etc/X11/xorg.conf.d/00-keyboard.conf. So X11 keybaord configuration has not been written. Reason is that xdm package has not been updated for this image. It's missing the changelog entries: ------------------------------------------------------------------- Wed Oct 18 15:01:24 UTC 2017 - sndirsch@suse.com - reintroduced /etc/X11/xdm/keytable script and the hook-up in /usr/lib/X11/display-manager to setup X11 keymaps, since YaST is not able to use localectl already during installation due to dbus and appropriate systemd services not running :-( (bsc#1046436) ------------------------------------------------------------------- Thu Oct 12 10:08:28 UTC 2017 - dimstar@opensuse.org - Have update-alternatives handle Xinit's integration of the displaymanager, replacing /etc/sysconfig/displaymanager. - Add a dummy entry for 'console' - which is special-cased in the display-manager script to 'exit early'. In order for it to become an option for update-alternatives, the target needs to exist. - Update /usr/lib/X11/display-manager to get the default-displaymanager from the update-alternative setting instead of reading it from /etc/sysconfig/displaymanager. - Remove DISPLAYMANAGER from displaymanager.sysconfig template. - Add xdm-with-update-alternative.patch so the needed changes can be applied for suse_version >= 1330 only, not breaking Leap 42.x. - All that together solves boo#1053863. Update xdm manually in order to create /etc/X11/xorg.conf.d/00-keyboard.conf for the first time. Then I've tested YaST keyboard module after installation. As explained before YaST keyboard module should use localectl set-keymap de-latin1-nodeadkeys instead of localectl --no-convert set-keymap de-latin1-nodeadkeys localectl --no-convert set-x11-keymap de pc105 nodeadkeys \ terminate:ctrl_alt_bksp localectl set-keymap is responsible for creating *also* the X11 keybaord layout and the mapping. I'm not sure, why this bug has been closed as fixed. Seriously. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c111 --- Comment #111 from Frederic Crozat --- (In reply to Stefan Dirsch from comment #110)

I cannot confirm this issue would have been fixed with the latest image. I've used

/mounts/dist/install/SLE-15-Installer-TEST/SLE-15-Installer-DVD-x86_64- Build321.5-Media1.iso

I've installed SLED with all available modules enabled. Registration key from

https://wiki.microfocus.net/index.php?title=YAST/reg_codes ("real" SCC)

So, you didn't test the latest build. You tested Alpha5 modules, on top of up-to-date SLE15 Installer.

I'm not sure, why this bug has been closed as fixed. Seriously.

Because people really tested the proper builds. Please either use proxy SCC or the additional "ALL Packages" iso. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c113 --- Comment #113 from Frederic Crozat --- (In reply to Stefan Dirsch from comment #112)

(In reply to Frederic Crozat from comment #111)

...

(In reply to Stefan Dirsch from comment #110)

...

I cannot confirm this issue would have been fixed with the latest image. I've used

/mounts/dist/install/SLE-15-Installer-TEST/SLE-15-Installer-DVD-x86_64- Build321.5-Media1.iso

I've installed SLED with all available modules enabled. Registration key from

https://wiki.microfocus.net/index.php?title=YAST/reg_codes ("real" SCC)

So, you didn't test the latest build. You tested Alpha5 modules, on top of up-to-date SLE15 Installer.

Aha. The installation procedure is just nowhere explained! sle15 is such a mess!

This is explained in every milestone release email for SLE15. It was also explained during the SLE15 lunch'n'learn which took place in Nuremberg some weeks ago.

...

...

I'm not sure, why this bug has been closed as fixed. Seriously.

Because people really tested the proper builds.

Please either use proxy SCC

Ok. Then this information is well/perfectly hidden!

...

or the additional "ALL Packages" iso.

Which I can find where ???

Please check Stefan Behlert email on devel which was sent minutes ago. It contains everything. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c116 --- Comment #116 from Stefan Dirsch --- (In reply to Frederic Crozat from comment #113)

...

...

So, you didn't test the latest build. You tested Alpha5 modules, on top of up-to-date SLE15 Installer.

Aha. The installation procedure is just nowhere explained! sle15 is such a mess!

This is explained in every milestone release email for SLE15.

"For testing SLE 15 with SCC you need a beta registration code." That was it. No information how to get thes keys, let alone SCC proxies ... I was happy that someone once told me about this webpage https://wiki.microfocus.net/index.php?title=YAST/reg_codes

It was also explained during the SLE15 lunch'n'learn which took place in Nuremberg some weeks ago.

I missed that one, since I was supposed to go to SUSE Labs conference. :-(

Please check Stefan Behlert email on devel which was sent minutes ago. It contains everything.

Unfortunately I do not read devel mails each minute. Ah. The boot option for proxy SCC now suddenly changed from "SCC_URL" to "regurl". That explains why my further testing didn't work either ... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c118 --- Comment #118 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #117)

Ok. With repositories of SCC proxy xdm package is up-to-date and X11 keyboard configuration is correct. I'm going to report a separate bug for the required localectl usage change in YasT2.

boo#1065264 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c120 Sergio Lindo Mansilla changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(slindomansilla@su | |se.com) | --- Comment #120 from Sergio Lindo Mansilla --- (In reply to Oliver Kurz from comment #119)

(In reply to Sergio Lindo Mansilla from comment #109)

...

Also verified from QA during manual testing of build 321.5.

Can we marked this ticket as verified fixed? Or is there yet work to do about it?

Sergio. This bug was initially reported for openSUSE Tumbleweed. Could you please verify TW and then set the bug to VERIFIED FIXED?

I have tried with openSUSE-20171028-i586-x86_64-Build0002 and the issue still happens on tumbleweed. Reopen? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c125 Stefan Hundhammer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ohering@suse.com --- Comment #125 from Stefan Hundhammer --- *** Bug 1042423 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c130 --- Comment #130 from Stefan Dirsch --- And please close boo#1074168 as dup of this new ibus bug. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1046436 http://bugzilla.suse.com/show_bug.cgi?id=1046436#c132 --- Comment #132 from Stefan Dirsch --- (In reply to Stefan Dirsch from comment #131)

Ah. There is already such an ibus bug (basically closed as INVALID, and apparently ibus won't be installed by default any longer). So closing this as fixed again.

boo#1073215 -- You are receiving this mail because: You are on the CC list for the bug.