Description of problem: I was testing the installation of Mageia-7-beta1-x86_64.iso in a VirtualBox and realized the keyboard is still QWERTY even if I select "French (azerty standard)" or "French (azerty latin9)". Version-Release number of selected component (if applicable): Mageia-7-beta1-x86_64.iso How reproducible: always Steps to Reproduce the 1st attempt 1. Choose French language from Boot menu, then "Installation" 2. When asked for the keyboard layout, keep the default "French (azerty standard" (a closing bracket is also missing, by the way) 3. When prompted for root password, username, user login and password, realize that the keyboard layout is still qwerty. Azerty is available in DE after reboot (tested with KDE and Gnome). Steps to Reproduce the 2nd attempt: 1. Choose French language from Boot menu, then "Installation" 2. When asked for the keyboard layout, choose "French (azerty latin9)" 3. When prompted for root password, username, user login and password, realize that the keyboard layout is still qwerty. Azerty becomes available in DE after reboot (tested with Gnome).
Priority: Normal => release_blocker
I have reproduced this fault, again in VirtualBox. Switching to the shell on vt2, I find the French keyboard layout has been correctly selected, as shown by typing and by the output of 'setxkbmap -query'. So it seems that the change of layout is not being passed to / acted on by mutter. In case this was a regression in mutter, I created a patched installer stage2 that contained the Mageia 6 version of mutter, but that didn't help.
Component: Release (media or process) => InstallerSummary: Mga-7-beta-1 : French AZERTY layout is not working when entering root + user login/password => Mga-7-beta-1 classical installer: French AZERTY layout is not working when entering root + user login/passwordAssignee: bugsquad => mageiatoolsCC: sysadmin-bugs => mageia
Is this a duplicate of bug 22745?
(In reply to Frédéric Buclin from comment #2) > Is this a duplicate of bug 22745? It looks very similar to what George described in bug 23632 indeed.
Not sure about bug 22745 - Frédéric sees the keyboard layout get changed, but to the wrong layout, whereas here we are seeing no layout change. Frédéric, could you try booting the installer then, after selecting the keyboard and reaching the partitioning choice screen, switch to the console on vt2 (Ctrl-Alt-F2 on real hardware, or RightCtrl-F2 in Vbox), and see if the keyboard layout is correct there by executing the command setxkbmap -query -display :0 But 23632 does look similar, but when I tested this with the Mageia 6 installer ISO, it worked fine.
Created attachment 10511 [details] Patch that fixes this bug
The key mapping is set correctly in the partitioning step, but gets reset to 'us' by the time we reach the user/password step. My guess is that some package is resetting the mapping in a post-install scriptlet. @Thierry, if you can think of a way to identify which package is the culprit, we could fix it in that package. If not, the attached patch will fix the problem, by reapplying the selected key mapping after the package installation step finishes.
Keywords: (none) => PATCHCC: (none) => thierry.vignaud
Strange. Might be the call to /usr/sbin/mageia-setup-keyboard in keyboard::write()
*** Bug 23916 has been marked as a duplicate of this bug. ***
CC: (none) => smelror
(In reply to Thierry Vignaud from comment #7) > Might be the call to /usr/sbin/mageia-setup-keyboard in keyboard::write() I already looked at that, but it doesn't do anything when run in the installer (/etc/sysconfig/keyboard doesn't exist, so it just exits).
(In reply to Martin Whitaker from comment #9) > (In reply to Thierry Vignaud from comment #7) > > Might be the call to /usr/sbin/mageia-setup-keyboard in keyboard::write() > > I already looked at that, but it doesn't do anything when run in the > installer (/etc/sysconfig/keyboard doesn't exist, so it just exits). And changing the patch to restore the keyboard layout as the first post-install action still fixes the bug. Unless you have any better ideas, I'll commit this fix. I've already patched the next round of beta1 ISOs to include it.
You could debug it by replacing setxkbmap by a script: - calling setxkbmap.real (renamed bin) on first run - logging subsequent calls (args, PPID, ...)
*** Bug 23909 has been marked as a duplicate of this bug. ***
CC: (none) => hamnisdude
(In reply to Thierry Vignaud from comment #11) > You could debug it by replacing setxkbmap by a script: > - calling setxkbmap.real (renamed bin) on first run > - logging subsequent calls (args, PPID, ...) I don't have time for this. If you do, please go ahead. If not, please accept the simple fix. I really don't want to have to keep patching stage2 manually each time I build the ISOs.
This bug seems to be fixed with Mageia-7-beta1-x86_64.iso "round 4".
(In reply to Sébastien Morin from comment #14) > This bug seems to be fixed with Mageia-7-beta1-x86_64.iso "round 4". It's not fixed, per se, as Martin patches something before generating the ISO's. Cheers, Stig
M7b2 Classic ISO 4 Dec 2018 x64 Confirm c14, the problem has gone. But re c15, I agree it should be fixed properly before closure. Certainly we cannot have last-minute patches for it.
CC: (none) => lewyssmith
Yeah but we need a real fix...
I'm still having issues. System lang set to en, with Norwegian as a second option. I chose Norwegian keyboard and it still wrote "Stig:\" when I tried to write "Stig-Ø" Will now try with a pure Norwegian setup and see how it goes.
Same issue with a pure Norwegian setup. "Stig/:" instead of "Stig-Ø". Got it wrong in comment 18.
(In reply to Stig-Ørjan Smelror from comment #18) > I'm still having issues. > > System lang set to en, with Norwegian as a second option. > I chose Norwegian keyboard and it still wrote "Stig:\" when I tried to write > "Stig-Ø" I've just tested this in Vbox, using the Mageia-7-beta1-x86_64.iso from 4th December (md5sum 0e7ccb8786cade01e006f5e675a6cd2b), and the Norwegian keyboard layout was still active when I reached the user management screen. If you switch to the console (Ctrl-Alt-F2), is the keyboard layout wrong there too? What does setxkbmap -display :0 -query report? If you boot into the installed system, what keyboard layout is selected? Please attach a copy of /root/drakx/ddebug.log.
(In reply to Thierry Vignaud from comment #17) > Yeah but we need a real fix... No, we need to release Mageia 7. For that, all we *need* is a fix that works.
Created attachment 10536 [details] report.bug.xz (In reply to Martin Whitaker from comment #20) > > setxkbmap -display :0 -query > On my first try, I got "en". Then I set "LANG=nb_NO.UTF-8 vmplayer" and keyboard layout was set to "no" until I clicked "Next". It was then reset to "en". So it gets set, but then reset in Vmware Player. It boots into a working system with system lang "en" and kbd layout "no". Cheers, Stig
Created attachment 10537 [details] ddebug.log.xz
(In reply to Stig-Ørjan Smelror from comment #22) > Created attachment 10536 [details] > report.bug.xz > > (In reply to Martin Whitaker from comment #20) > > > > setxkbmap -display :0 -query > > > > On my first try, I got "en". > > Then I set "LANG=nb_NO.UTF-8 vmplayer" and keyboard layout was set to "no" > until I clicked "Next". It was then reset to "en". I've never used vmplayer, but if setting LANG outside the VM affects the behaviour inside the VM, it's not a very good virtual machine.
I've now tested this using vmplayer. After selecting the keyboard layout as Norwegian, I get Norwegian layout in both the custom partitioning stage and in the user/password stage, i.e. the fix is working for me. BTW, to get to the installer console in vmplayer, the key combination is Ctrl-Alt-Space-F2
However, I have now identified what is resetting the keyboard layout. It is the 'udevadm trigger --type=devices' that is called at the end of the formatting step.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23946
I have seen this for Swedish with QWERTY as well in the net iso installer before.
(In reply to Martin Whitaker from comment #26) > However, I have now identified what is resetting the keyboard layout. It is > the 'udevadm trigger --type=devices' that is called at the end of the > formatting step. Nice catch :-) ! Now the questions are: Why is this suddenly an issue? And how to fix/workaround it?
Maybe using --subsystem-match=SUBSYSTEM or better blacklisting input stuff using --subsystem-nomatch=SUBSYSTEM if DURING_INSTALL is set?
aka using either --subsystem-match=block or --subsystem-nomatch=input (to be tested)
To answer comment #28, it's probably since we include input rules (aka since February)
I've confirmed that --subsystem-match=block fixes this bug and doesn't reintroduce bug 22059. This won't help bug 23946 - that one is triggered by the call to mageia-setup-keyboard.
Cool, can you commit that?
Attachment 10511 is obsolete: 0 => 1
Fixed in git (the bot still isn't working :-( )
Keywords: PATCH => (none)
Awesome. Now we wait for the new images with the new kernel to become available :-)
Hello, I tried an installation from beta1-DVD x86_64. I tried to add supplemental sources after the partitioning step. This step configures the network. Editing the hostname during this phase, I got QWERTY layout instead of the French selected one.
CC: (none) => yves.brungard_mageia
Hello, This bug is now fixed with Mageia-7-beta2-x86_64.iso (round 1) (from a user's perspective).
Thanks for testing, Sébastien.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Does this bug affect also Mageia 6 installer? In this case, it should be backported to Mageia 6 for netinstall.
(In reply to papoteur from comment #39) > Does this bug affect also Mageia 6 installer? > In this case, it should be backported to Mageia 6 for netinstall. Just did 3 tests using Mageia-6-x86_64-DVD.iso : Test 1 : French selected in F2 menu + default French language + default French layout => Azerty keyboard is available in the User Management page. Test 2 : French NOT selected in F2 menu + French language (Europe) selected + default French layout => Azerty keyboard is available in the User Management page. Test 3 : French NOT selected in F2 menu + French langauge (America) selected + default French layout => Azerty keyboard available. To conclude: Mageia 6 classical installer is NOT affected by this bug. I can't confirm anything about Mga6.1 netinstall for the moment.
(In reply to Sébastien Morin from comment #40) > I can't confirm anything about Mga6.1 netinstall for the moment. As for Mageia-6.1-netinstall-nonfree-x86_64.iso it is now confirmed in bug 23632