Description of problem: I have a default install in Chinese successfully,however,after the reboot,I can not input Chinese though I choose the langage mode on the top-right corner from "en"to "zh".Then I have a default install in French,this time,the default support langage is "Bambara",terrible. Version-Release number of selected component (if applicable): f18 TC7 x86-64 How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
What does /etc/sysconfig/i18n say immediately after installation? Also, please attach /var/log/anaconda/packaging.log to this bug report.
This may be fixed by the combo of bug 873865 and bug 868869
Created attachment 639836 [details] i18n
Created attachment 639837 [details] packaging.log
Jesse - yes, I think you are right.
lnie, can you re-test this with Beta RC1 and check whether it's fixed? Thanks!
(In reply to comment #6) > lnie, can you re-test this with Beta RC1 and check whether it's fixed? > Thanks! Hi Adam, I tested this again with Beta RC1(actually,I have tested it 3 times).the result is the same as the previous one.
Setting back to ASSIGNED, then.
So, is this bug report about langauges not being set up or input method packages not being installed? I just did Chinese and French installs with a post-beta tree, and I see things translated as expected from anaconda, through grub, firstboot, and the gnome-shell crash dialog.
Chris: from the initial report, this looks to be about the post-install state: "however,after the reboot,I can not input Chinese though I choose the langage mode on the top-right corner from "en"to "zh"" it may be that some packages that are needed to make CJK input work do not get installed. could even be related to the langpacks problem?
Perhaps, but I don't think we'll know until it gets re-tested by someone who knows to spot that things are wrong.
I could probably fake enough Japanese input knowledge to figure this one out if I really have to, but we'll see if someone better can do it first.
Actually,I am able to type Janpanese after a Janpanese install(f18 final TC1), But I am unable to type Chinese after an Chinese install.though I am able to change "en" to"zh".I have to add"Chinese(Intelligent pinyin)"to the"input source"of"Region&Language"to type Chinese,even though I make a Chinese install.(the system language is Chinese， Activities:活动，Terminal:终端）
That doesn't really narrow down whether this is an anaconda problem or something else, though. Do you have the correct input method packages installed? To the best of my knowledge, there's nothing really that anaconda needs to do to set up a particular input method as the default, nor have we done so in the past. I'm starting to think this is not an anaconda problem.
I can confirm at least one part of this bug: after installing smoke6 in French, I get keyboard layouts English and Bambara. This seems wrong. Not sure if these two are really the same bug, or something different.
(In reply to comment #14) > To the best of my knowledge, there's nothing really that > anaconda needs to do to set up a particular input method as the default, nor > have we done so in the past. Hi Chris,I have make f15 and f17 Chinese install before I report the bug,and after a reboot,I'm able to type Chinese without do anything.As for the Janpanese installtion ,the bug is fixed.I can type Janpanese after a reboot.
(In reply to comment #15) > I can confirm at least one part of this bug: after installing smoke6 in > French, I get keyboard layouts English and Bambara. This seems wrong. Not > sure if these two are really the same bug, or something different. Hi Adam,it seems that these two are the same bug,as I have a Janpanese install,the keyboard layouts English and Bambara.But,this bug dosen't occur again in a Janpanese install of f18 Final TC1
Accoding to lnie's description and my experience, I think the main input related packages has been installed, but it is not active by default. That's why it worked well after adding the input method to the "input source".
(In reply to comment #15) > I can confirm at least one part of this bug: after installing smoke6 in > French, I get keyboard layouts English and Bambara. This seems wrong. Not > sure if these two are really the same bug, or something different. I have just installed a system with 'French' layout in the installation and in Gnome I got French, Bambara and English. But since configuration files look as expected (only 'fr' layout and console keymap listed), there is nothing more Anaconda could do. See bug #878433 for more info. The support for input methods is something separate and I'm afraid anaconda can hardly guess which languages need input methods installed. Moreover it cannot configure this for a user that doesn't exist (during installation).
Still occur in f18 Final TC3 x86_64.
Created attachment 666654 [details] patch for gnome-settings-daemon IIUC, the original bug is specific to the zh_CN locale and should be fixed with this patch. For upstream we should have a better user experience in GNOME 3.8 with the initial-setup tool.
gnome-settings-daemon-3.6.3-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gnome-settings-daemon-3.6.3-2.fc18
Proposing as NTH, we should fix this.
Package gnome-settings-daemon-3.6.3-2.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 gnome-settings-daemon-3.6.3-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20738/gnome-settings-daemon-3.6.3-2.fc18 then log in and leave karma (feedback).
Discussed at 2012-12-21 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-21/f18final-blocker-review-7.2012-12-21-18.33.log.txt . Accepted as NTH for obvious reasons - this is v. significant for Chinese users, and can't be fixed with an update for DVD installs.
gnome-settings-daemon-3.6.3-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
Tested it in the newly f18 final TC4 x86_64,this bug seems to be fixed.