Description of problem: gnome-initial-setup has very a nice interface to choose language and keyboard layout etc. However the initial gnome session does not start in the language selected in gnome-initial-setup (rather it always seems to start in en_US.utf8). Version-Release number of selected component (if applicable): gnome-initial-setup-0.8-3.fc19 Steps to Reproduce: 1. install latest F19 (desktop) 2. boot to gnome-initial-setup 3. choose Japanese language for example 4. start gnome desktop 5. logout and login again to gnome Actual results: 4. desktop runs in English not Japanese 5. desktop runs in Japanese Expected results: 4. initial desktop to run in selected language (Japanese not English)
I did the install of Fedora-19-Alpha-TC2-x86_64-DVD.iso in Japanese, did choose “Deutsch” (German) in gnome-initial-setup and the Gnome Desktop came up in Japanese. So although I did choose a different language in gnome-initial-setup, it seems to use the system language: [mfabian@Fedora-19-Alpha-TC2-x86_64-DVD ~]$ cat /etc/locale.conf LANG="ja_JP.UTF-8" [mfabian@Fedora-19-Alpha-TC2-x86_64-DVD ~]$
Problem still exists in Fedora-19-Alpha-TC4-x86_64-netinst.iso
I've also faced this problem. I've first selected Czech, immediately changed to English (US) and desktop run with cs_CZ.UTF-8.
I am not sure how easy this is to fix. I assume gnome-session runs gnome-initial-setup, in which case the desktop session is already running in the system locale so if the user locale is changed by gnome-initial-setup it would be better to exit the session after gnome-initial-setup finishes.
I assume this only happens with the 'user session' incarnation of g-i-s that runs when you create a user during the install, not the 'pre-GDM' incarnation of g-i-s that runs when you *don't* create a user during the install?
For both AFAICR but will retest again with RC2.
you'd think at least the 'pre-gdm' case would be fixable, since it must log in to the user account after creating the user...
Actually the pre-gdm case seems fixed/working now: I did a Japanese install and selected en_GB for my new gnome user and indeed the session does run un en_GB. So I guess the problem left now is just for existing users. Anyway like control-center it might be better (to offer) to logout after changing the language of an existing user.
Discussed at 2013-05-20 freeze exception review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-20/f19beta-blocker-review-7.2013-05-20-16.07.log.txt . Rejected as an FE issue: we're close to Beta now, and it's not really worth twiddling with g-i-s and potentially breaking things just to fix this. Should be fixed for Final, though.
(In reply to Adam Williamson from comment #5) > I assume this only happens with the 'user session' incarnation of g-i-s that > runs when you create a user during the install, not the 'pre-GDM' > incarnation of g-i-s that runs when you *don't* create a user during the > install? This problem still exists in Fedora 20 Alpha RC3.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Moving to F20 per c#10. Mike, current status?
The problem still exists in the released Fedora 21 version. - Install Fedora-Live-Workstation-x86_64-21-5.iso in Japanese - create a user during the installation - log in and choose German in gnome-initial-settings -> Desktop still runs in Japanese, not German - log out and log in again -> now the desktop runs in German.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.