Description of problem: when using US Int / NZ English there is a diffence in the way the 32 bit and 64 installs behave with various functions( ~, ',^,") eg: 32 bit: portégé 64 bit: port'eg'e (this is the correct US Keyboard setting) Version-Release number of selected component (if applicable): 7-beta2-i586.iso DATE.txt: Wed Jan 30 7-beta2-x86_64.iso DATE.txt: Wed Jan 30 How reproducible:every time Steps to Reproduce: 1. install Multi DE system from both .iso with US Int keyboard/NZ English choices 2. boot into both system and use kwrite to enter: portégé 3.one will be correct64bit), the other not so (32bit)
Keywords: (none) => 7beta2
Created attachment 10701 [details] 32bit report.bug.xz install is on same hardware
Created attachment 10702 [details] 64bit report.bug.xz install is on same hardware / different partition
(In reply to ben mcmonagle from comment #0) Your "32bit" keyboard behaves like a US-International keyboard https://en.wikipedia.org/wiki/US-International#US-International Your "64bit" keyboard behaves like a normal US keyboard. That is what should happen, given that in the 32bit install the us-intl keyboard was loaded, but in the 64bit install the us (so non-intl) one. Another difference is, that the 32bit install doesn't have en_US in "selectLanguage: pack_langs:" (See below the ****** line for the matching parts of the installer logs) Are you sure you made the exact same choices in the selectLanguage and selectKeyboard steps for both installs? I don't know what the warnings (in both installs), when starting the selectLanguage step, mean. ************************************************************************* *32bit:* Window manager warning: Locale not understood by C library, internationalization will not work (mutter:605): mutter-WARNING **: 01:48:54.688: Could not load library [/usr/lib/mutter/plugins/default.so (/usr/lib/mutter/plugins/default.so: cannot open shared object file: No such file or directory)] Unable to load plugin module [/usr/lib/mutter/plugins/default.so]: /usr/lib/mutter/plugins/default.so: cannot open shared object file: No such file or directory* starting step `selectLanguage' * i18n_env: lang:en_NZ country:NZ locale|lang:en_NZ.UTF-8 locale|country:en_NZ.UTF-8 LANGUAGE:en_NZ:en_AU:en_GB:en * selectLanguage: pack_langs: en_NZ:en_AU:en_GB:en utf8-flag: 1 *64bit:* Window manager warning: Locale not understood by C library, internationalization will not work (mutter:604): mutter-WARNING **: 03:28:53.071: Could not load library [/usr/lib64/mutter/plugins/default.so (/usr/lib64/mutter/plugins/default.so: cannot open shared object file: No such file or directory)] Unable to load plugin module [/usr/lib64/mutter/plugins/default.so]: /usr/lib64/mutter/plugins/default.so: cannot open shared object file: No such file or directory* starting step `selectLanguage' * i18n_env: lang:en_NZ country:NZ locale|lang:en_NZ.UTF-8 locale|country:en_NZ.UTF-8 LANGUAGE:en_NZ:en_AU:en_GB:en * selectLanguage: pack_langs: en_NZ:en_AU:en_GB:en:en_US:en utf8-flag: 1 *32* * starting step `selectKeyboard' * lang:en_NZ charset:iso-8859-1 font:DejaVu Sans 12 consolefont:lat1-16 * lang:en_NZ charset:iso-8859-1 font:DejaVu Sans 12 consolefont:lat1-16 * loading keymap us-intl * running: setxkbmap -option * running: setxkbmap us -variant alt-intl -model pc105 -option compose:rwin -compat * step "selectKeyboard" took: 0:00:06 *64* * starting step `selectKeyboard' * lang:en_NZ charset:iso-8859-1 font:DejaVu Sans 12 consolefont:lat1-16 * lang:en_NZ charset:iso-8859-1 font:DejaVu Sans 12 consolefont:lat1-16 * loading keymap us * running: setxkbmap -option * running: setxkbmap us -variant -model pc105 -option compose:rwin -compat * step "selectKeyboard" took: 0:00:06
CC: (none) => marja11Keywords: (none) => NEEDINFO
(In reply to Marja Van Waes from comment #3) CC'ing the mageia tools maintainers for those warnings: > > *32bit:* > Window manager warning: Locale not understood by C library, > internationalization will not work > > (mutter:605): mutter-WARNING **: 01:48:54.688: Could not load library > [/usr/lib/mutter/plugins/default.so (/usr/lib/mutter/plugins/default.so: > cannot open shared object file: No such file or directory)] > Unable to load plugin module [/usr/lib/mutter/plugins/default.so]: > /usr/lib/mutter/plugins/default.so: cannot open shared object file: No such > file or directory* starting step `selectLanguage' > > *64bit:* > > Window manager warning: Locale not understood by C library, > internationalization will not work > > (mutter:604): mutter-WARNING **: 03:28:53.071: Could not load library > [/usr/lib64/mutter/plugins/default.so (/usr/lib64/mutter/plugins/default.so: > cannot open shared object file: No such file or directory)] > Unable to load plugin module [/usr/lib64/mutter/plugins/default.so]: > /usr/lib64/mutter/plugins/default.so: cannot open shared object file: No > such file or directory* starting step `selectLanguage'
CC: (none) => mageiatools
(In reply to Marja Van Waes from comment #3) > (In reply to ben mcmonagle from comment #0) > > > Are you sure you made the exact same choices in the selectLanguage and > selectKeyboard steps for both installs? > > yes, I re-ran both installs to be sure
Despite several attempts, the only way I can reproduce this is to deliberately select "US keyboard (international)" at the keyboard step. "* selectLanguage: pack_langs:" seems to randomly include/exclude en_US, but that had no effect on the keyboard layout. But this is in VBox. The actual keyboard type might matter. But I can't think why it would be different between 32-bit and 64-bit.
CC: (none) => mageia
@ Ben If this bug is still valid , then please take screenshots of the selectKeyboard step for both the 32bit and the 64bit install, both with the choice it defaults to, and (if you change the default) with the keyboard you select. Pressing "F2" when you're in that screen, will create a screenshot. After install you'll find the screenshots in /root/DrakX-screenshots/ Note that you need the "US keyboard" and _not_ "US keyboard (international)"
Oh, and attach them, of course ;-)
Created attachment 10840 [details] default keyboard (i586)
Created attachment 10841 [details] user selected keyboard (i586)
Created attachment 10842 [details] default keyboard (x86_64)
Created attachment 10843 [details] user selected keyboard (x86_64)
well, the keyboard response is now the same. but I am not sure if it is correct. will try the plain old US keyboard tomorrow and advise. Maybe I have been doing it wrong for 15 years with windows, and then 15 years with Linux ;-) The following keystrokes give the same, but incorrect outcome (^= shift, > = spacebar) ^"^Port'eg'e^" => ortégé but ^">^Port'eg'e^"> => "Portégé"
Reading the Wikipedia reference Marja gave in comment 3, that does seem to be the correct behaviour.
seems to correct now
Status: NEW => RESOLVEDResolution: (none) => FIXED