Please do not reply directly to this email. All additional comments should be made in the comments box of this bug.
https://bugzilla.redhat.com/show_bug.cgi?id=734076
--- Comment #1 from Cheng-Chia Tseng pswo10680@gmail.com 2011-09-02 11:37:08 EDT --- Below is "the 5 things you should check when gicn cannot be activated" by gcin author, translated by me.
Quote If you cannot make gcin activated, please check:
1. Execute 'pgrep gcin'
Can you see gcin process ID (a number)? If you can, please go to 3 directly.
2. Execute 'gcin' directly to see if there is any error message.
If the last line is "IMOpenIM failed. Maybe another XIM server is running." That means another XIM server might be running. So try to kill gcin / scim/ibus 's process and execute gcin again.
3. Check whether XMODIFIERS is set consistent or not.
Normally, we can use printenv to check content of environment variables.
But there are too many places where you can set environment variables, using terminal to check may not fit the actual values of applications using. It will be more precise to see proc file system directly.
Execute this command:
$ pgrep gcin 7438 $ strings /proc/7438/environ
This file contains all the environment variables content of this process. You can check the content of XMODIFIERS. You can use the same way to check other programs, eg. pgrep firefox.
gcin can be set without its own XMODIFIERS, but applications has to set to "XMODIFIERS=@im=gcin".
4. Executing "gtk-query-immodules-2.0" (or allike), you should see:
"/usr/lib/gtk-2.0/immodules/im-gcin.so" "gcin" "gcin Input Method" "gcin" "/usr/share/locale" "zh:ja"
If you cannot see those message above, it implies im-gcin.so is not installed.
5. /etc/gtk-2.0/gtk.immodules.lib should have the same messages in 4. If it don't, you can execute:
# gtk-query-immodules-2.0 > /etc/gtk-2.0/gtk.immodules.lib /Quote
The result is that gcin 1.6.1 package does not pass 5; however, after I did the command provided by gcin author and log in again, gcin did not work still.
I doubt the process separating single gcin pacakge into 4 subpackages might has something worong.