Description of problem: When the application starts not using the default locale, the new application with the new locale will not be able to utilised any LE. Version-Release number of selected component (if applicable): im-sdk-12.1.1-3.svn2208 How reproducible: Always Steps to Reproduce: 1.Log in as normal user at GDM with CJKI locale 2.in g-t, LANG=ja_JP.UTF-8 gedit 3.alt-tab to gedit, CTRL-SPACE Actual results: Nothings happens Expected results: Should be able to input in ja using CannaLE Additional info:
How about LANG=ko_KR.UTF-8 ?
Are you sure that the iiim immodule is selected at the Input Method menu which is popup by the right click?
My apologies. Using CannaLE was a bad test case. I dont know why the rest of the LE were not working properly as well yesterday. This bug is CannaLE specific. Test Case: 1) in g-t, LANG=ja_JP.UTF-8 gedit 2) Ctrl-SPACE in the gedit application
Well, it happens on the enforcing mode for SELinux. it was why I didn't see this problem on my box so that I disabled SELinux. the below is a log of avc message: type=KERNEL msg=audit(1109284584.779:1262878): avc: denied { read } for pid=4204 exe=/usr/sbin/htt_server name=default.cbp dev=sda2 ino=233878 scontext=user_u:system_r:i18n_input_t tcontext=system_u:object_r:usr_t tclass=file type=KERNEL msg=audit(1109284584.792:1262888): avc: denied { write } for pid=4204 exe=/usr/sbin/htt_server name=IROHA dev=sda2 ino=239841 scontext=user_u:system_r:i18n_input_t tcontext=user_u:object_r:var_run_t tclass=sock_file type=KERNEL msg=audit(1109774881.210:4800416): avc: denied { connectto } for pid=5645 exe=/usr/sbin/htt_server path=/var/run/.iroha_unix/IROHA scontext=root:system_r:i18n_input_t tcontext=root:system_r:initrc_t tclass=unix_stream_socket
If you disabled selinux, you need to relabel when you turn SELinux back on. THe problem here is that /var/run.iroha_unix is mislabled. You can restorecon -R -v /var to clean this up but there may be other mislabeled files. Best to relabel by touch /.autorelabel reboot If you still see avc messages I will clean them up. Dan
Err, I only disabled selinux, so it just worked for me and I didn't see any problem like not working IIIMF due to selinux stuff. presumably people who encountered this problem should installed it with enabling selinux. so I wonder if there was mislabeled stuff.