Bug 853877

Neither keyboard nor language settings are a part of alpha criteria.

(In reply to comment #1)
> Neither keyboard nor language settings are a part of alpha criteria.

=> Moved to beta blocker.

Patch for the language part pushed to anaconda git repository. However I have no idea how to tell systemd which keymap it should load after reboot (X configuration should work, because we create a configuration file in xorg.conf.d). Lennart, could you please tell me what file(s) systemd-localed is looking at for configuration?

*** Bug 854958 has been marked as a duplicate of this bug. ***

Does this include timezone too or should I file separately for that?

(In reply to comment #5)
> Does this include timezone too or should I file separately for that?
I believe timezone settings are okay, what problem do you see? If you run 'date', what timezone does it display to you? And is '/etc/localtime' a valid symlink to the timezone you have selected in the installation? If not, please file a separate bug.

Okay thanks Vratislav - I better recheck then.

Ok I filed bug 856995 for the timezone issue (reproduced with Alpha RC3).

(In reply to comment #3)
> Patch for the language part pushed to anaconda git repository. However I
> have no idea how to tell systemd which keymap it should load after reboot (X
> configuration should work, because we create a configuration file in
> xorg.conf.d). Lennart, could you please tell me what file(s) systemd-localed
> is looking at for configuration?

/etc/vconsole.conf

See vconsole.conf(5) for more information.

I'd recommend simply talking to localed and let it do the necessary conversion from X11 → console keymap. That's what GNOME3 later on does, too. This is documented here:

http://www.freedesktop.org/wiki/Software/systemd/localed

Discussed at 2012-09-26 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-09-26/f18-beta-blocker-review-1.2012-09-26-16.03.log.txt . Accepted as a Beta blocker (in fact should have been Alpha blocker), as a conditional violation of criterion "Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria must boot to a working graphical environment without unintended user intervention. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied" : our usual way of handling keymap issues is to say that they violate this criterion, in the case where you set a root password or an encrypted partition passphrase which uses a character that's typed differently in the chosen keymap vs. the one that is actually (incorrectly) used (usually en-US). We may institute an explicit criterion for this though, in future.

anaconda team, what's the status of this? pace https://bugzilla.redhat.com/show_bug.cgi?id=858591 , we know anaconda is at least making an effort to write out localization configuration as of beta, but stuffing it up rather badly at present. Is there an attempt to configure the keymap used in consoles on the installed system? Is it expected to be working at present or not?

(In reply to comment #11)
> anaconda team, what's the status of this? pace
> https://bugzilla.redhat.com/show_bug.cgi?id=858591 , we know anaconda is at
> least making an effort to write out localization configuration as of beta,
> but stuffing it up rather badly at present. Is there an attempt to configure
> the keymap used in consoles on the installed system? Is it expected to be
> working at present or not?
I'm just finishing the patch for writing out console keymap configuration, but I have some troubles with using systemd-localed in the installation environment.

Patch set sent to anaconda-patches list.

This was set to MODIFIED on 10-12, but no comment was added, nor was the 'fixed in version' field changed. Has this been committed to anaconda? Has it made it into a release yet? Can someone please clarify?

(In reply to comment #14)
> This was set to MODIFIED on 10-12, but no comment was added, nor was the
> 'fixed in version' field changed. Has this been committed to anaconda? Has
> it made it into a release yet? Can someone please clarify?
This was part of the 4b98eab34f310c2704ec24b417bdf919c413fa1d commit, that was pushed on 10-12. I'm not sure why this patch was not listed in the bodhi update.

So this needs testing with 18.17 or higher.

anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18

anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18

Package anaconda-18.18-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.18-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18
then log in and leave karma (feedback).

anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18

I tried with Beta TC6 (anaconda 18.19, DVD and Live) and I received a system with the German language and the German keyboard by default. Closing as fixed.