Description of problem: I am using Fedora-Live-Workstation-x86_64-rawhide-20140702 with GNOME.3.13.3. I can't use any input method in gtk applications but i could use input methods in terminal. In terminal if i set export GTK_IM_MODULE=ibus and then open gedit then i can use input method in it Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Using g-c-c, choose Japanse kana kaji as input method 2. Open gedit and try to type characters asa SPACE 3. Actual results: User could see latin characters Expected results: User should see Japanese characters Additional info:
Reproduced here too. ja_JP.utf8 desktop is okay but not en_US.utf8 locale.
But this also seems to happen on MATE so moving to ibus.
(In reply to anish from comment #0) > In terminal if i set export GTK_IM_MODULE=ibus and then open gedit then i > can use input method in it Transferring to imsettings.
After having run im-chooser to turn on ibus in Mate, I seem no longer to reproduce in Gnome...
Created attachment 914658 [details] ~/.cache/imsettings/log imsettings log file from another a/c where im-chooser has not been run and can still reproduce problem under en_US.utf8
(In reply to Jens Petersen from comment #4) > After having run im-chooser to turn on ibus in Mate, > I seem no longer to reproduce in Gnome... because imsettings manually sets GTK_IM_MODULE according to .xinputrc. the difference is whether it is ibus or gtk-im-context-simple. Updates from the conversation on irc last week: This happens because imsettings-gsettings sub-package is missing. so imsettings figured out/can't determine if the desktop has the gtk support. I don't know why it didn't get pulled in. need to check that.
https://kojipkgs.fedoraproject.org//work/tasks/8744/7108744/fedora-live-workstation-7426bd8.ks Apparently the kickstart file explicitly dropped imsettings-* packages.
(In reply to Akira TAGOH from comment #7) > Apparently the kickstart file explicitly dropped imsettings-* packages. Can you give the argument for having imsettings installed under GNOME?
s/imsettings-*/imsettings*/ Given that they want to drop imsettings* packages completely, they need to add `-imsettings-qt' into the kickstart file as well to drop it too, because they explicitly add qt there and it pulls imsettings-qt in according to the comps. % rpm -q --whatrequires imsettings im-chooser-common-1.6.4-3.fc21.x86_64 % rpm -q --whatrequires im-chooser-common im-chooser-1.6.4-3.fc21.x86_64 % rpm -q --whatrequires im-chooser imsettings-qt-1.6.7-3.fc21.x86_64 (In reply to Jens Petersen from comment #8) > (In reply to Akira TAGOH from comment #7) > > Apparently the kickstart file explicitly dropped imsettings-* packages. > > Can you give the argument for having imsettings installed under GNOME? Is it time to drop it completely maybe? dunno. Anyway I don't have anything I can do in imsettings for this. reassigning to spin-kickstarts.
Okay I just committed a fix to fedora-workstation-packages.ks which should hopefully fix this. https://git.fedorahosted.org/cgit/spin-kickstarts.git/commit/?id=ba1430e757abdc25814f567cf819c317bae7f016
Discussed in 2014-08-20 Freeze Exception Review Meeting [1]. AcceptedFreezeException - Without proper input method support, many users would be unable to test Alpha. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-08-20/
Looks fine to me with Fedora-Live-Workstation-x86_64-21-20140820.iso
Let's close it, then. VERIFIED status doesn't mean much without bodhi.