Bug 864007 - Chosen keyboard layout not set after install
Chosen keyboard layout not set after install
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-10-08 06:30 EDT by Jóhann B. Guðmundsson
Modified: 2012-10-08 10:09 EDT (History)
4 users (show)

See Also:
Fixed In Version: anaconda-18.8-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-10-08 10:09:25 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jóhann B. Guðmundsson 2012-10-08 06:30:34 EDT
Description of problem:

Set Icelandic keyboard layout in Anaconda, install and then boot into multi-user.target.

Version-Release number of selected component (if applicable):

What ever was on the alpha ( Have not tested with beta tc so this might be fixed already )

How reproducible:


Steps to Reproduce:
1. See description
Actual results:

Icelandic keyboard layout not present after installed system

Expected results:

Being able to type Icelandic characters in terminal

Either kernel command line containing 

"vconsole.keymap=is-latin1 vconsole.font=latarcyrheb-sun16" or the necessary changes made to /etc/vconsole.conf as in 


Additional info:

Note that the /etc/sysconfig/i18n is now considered an legacy config file ( but still backwards compatible as in systemd will pick these changes up although I think the kernel parameters SYSFONT and FONT are being ignored/deprecated ) thus the installer,firstboot and probably bunch of other stuff to needs to be updated to use and make the necessary changes to /etc/vconsole.conf instead.

see [1] for details about the config file and the new kernel commandline parameters 

Comment 1 Chris Lumens 2012-10-08 10:09:25 EDT
Yes, this is fixed post-alpha.

Note You need to log in before you can comment on or make changes to this bug.