Description of problem: The selection and enabling of keyboard layout is designed by a technically inclined person. It is not easily understandable. Version-Release number of selected component (if applicable): 18.29.2 How reproducible: Always Steps to Reproduce: 1. Leave English as language as error messages/reporting are better in English 2. Click Keyboard selection icon 3. Start pondering on why no other keyboards are displayed in the keyboard selection window than English 4. After a while realize that a small non-labeled plus sign must be clicked to produce a selection of keyboard layouts to choose from 5. Move the selected keyboard to the top as the default as described 6. Click a special char in the test window and wonder, why the char appearing is the one from the English keyboard 7. Hm, will probably be fixed when clicking done 8. Verify on the main window, that the non-english keyboard is displayed as selected 9. Continue configuring the installation and discover, that it is still using the English keyboard layout !? 10. Hm, return to the keyboard selection window and read something about 'layout switching' 11. Why on earth should I care about layout switching ? I only have one keyboard ! 12. Ah well, let us define a strange key combination for this 13. After this then let us try the key combination 14. Hooray, now the chars pressed on the keyboard actually also are displayed Actual results: Non-English keyboard not selected Expected results: Non-English keyboard selected Additional info: When a keyboard layout is defined as default, it should automatically be selected and used. There should be no need for activating it by a key combination.
Máirín, any suggestions for the UI layout?
(In reply to comment #0) > Description of problem: > The selection and enabling of keyboard layout is designed by a technically > inclined person. It is not easily understandable. > > Version-Release number of selected component (if applicable): > 18.29.2 > > How reproducible: > Always > > Steps to Reproduce: > 1. Leave English as language as error messages/reporting are better in > English > 2. Click Keyboard selection icon > 3. Start pondering on why no other keyboards are displayed in the keyboard > selection window than English > 4. After a while realize that a small non-labeled plus sign must be clicked > to produce a selection of keyboard layouts to choose from > 5. Move the selected keyboard to the top as the default as described > 6. Click a special char in the test window and wonder, why the char > appearing is the one from the English keyboard > 7. Hm, will probably be fixed when clicking done > 8. Verify on the main window, that the non-english keyboard is displayed as > selected > 9. Continue configuring the installation and discover, that it is still > using the English keyboard layout !? > 10. Hm, return to the keyboard selection window and read something about > 'layout switching' > 11. Why on earth should I care about layout switching ? I only have one > keyboard ! If I understand it correctly, you had two layouts in the list, right? This means you had "two keyboards" which really is not much usable without key combination for layout-switching, especially for the installation where you have no other option to switch between layouts. I'll have a look at what we can do with activation of the default layout when it is changed.
Please see also the bug #859465.
*** Bug 882558 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > I'll have a look at what we can do with activation of the default layout > when it is changed. Patch for that has been posted to anaconda-patches. If you think this should be fixed in Fedora 18, please propose this bug as a NiceToHave by adding F18-accepted to the Blocks: field.
Patch pushed to master. No additional info needed here.
I was opening a new bugreport, but I found out this one, so I attach it as a comment. Description of problem: There is something wrong in Fedora installation, when Anaconda asks you the root and LUKS passwords. If you have a non English keyboard, you will probably fail entering the root password, since there is not an alert about which keytable are you currently using. Instead, when you set the LUKS password, there is. I tried many times the following procedure on fresh virtual machines: Here you can find an image of Italian keymap, it should helps you to better understand the problem http://upload.wikimedia.org/wikipedia/commons/3/33/Italian_keyboard_touchtyping.png Steps to Reproduce: 1. Steps I followed in Fedora KDE. I did not try on Fedora Gnome. Let assume that we need an identical password for LUKS and root. Let assume also that this password contains a '@' char. 2. Start installation. Select Italian language. 3. Select Italian keymap in Anaconda keyboard settings. 4. Setup a LUKS password. You will be prompted to enter the LUKS password with a US keymap. Since I am using an Italian keyboard, with US keymap, to enter the char '@' I have to push the buttons SHIFT+2. 5. While the installation is in progress, click on "setup root password". The password prompt does not show which keymap are you using. Assuming that I am still using US keymap, to enter the char '@' I have to push the buttons SHIFT+2. Actual results: During boot procedure, the LUKS password prompt is still in US keymap. So to enter to enter the char '@' I have to push the buttons SHIFT+2. Instead, when I try to enter root password in the system, my keymap is (obviously) Italian and I can simply press the ALTGR+ò to enter the char '@'. This creates a lot of confusion on both technical and non technical users. Expected results: Having Italian keymap immediately after selecting the language at Anaconda start. Additional info: Fedora 18 KDE Beta
On Live installations (KDE), the keyboard configuration in the Anaconda installer applies only to the installed system. You should use the desktop environment's tools to setup keyboard configuration for the installation process. Please see bug #886463 that contains some more info.
We should really document the somewhat messy state of keyboard selection during installation for final release, assuming it's too late to fix any of the commonly-encountered 'huh?' moments. Nominating this bug as commonbugs to cover that.
*** Bug 888157 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
In current F19 Beta TC4, layouts are activated as they are moved to the top of the list in the Keyboard spoke, and there is an indicator superimposed on the installer at all times. This makes things a lot clearer. Jens' first 'problem' - the need to click the + button to add a layout - isn't solved, but that's a standard design for GNOME and anaconda now, so I don't think we're expecting that to change. Closing.