Comment 2 for bug 107391

Ming Hua wrote:
>> - XMODIFIERS set to @im=scim
>
> It may not be related to the bug, but this setting is incorrect. The
> correct setting for XMODIFIERS is @im=SCIM, uppercase. However with
> GTK_IM_MODULE set to scim, this environment variable shouldn't have any
> effect.
>
> Would you please set GTK_IM_MODULE to xim and test again? Thanks.
>
Sorry for the late reply.　It looks like there are two specific
problemes, actually: applications hanging up when scim is the IM, and
problems when converting from kana to kanji, specific to scim-anthy.

First, I removed all the settings related to IM from my .xsession and my
bashrc, to test it on a per application basis. When I do:

GTK_IM_MODULE=xim mozilla-thunderbird

then it launches correctly. If I replace xim by scim in the above
command, it does not work anymore. scim is effectively launched, since I
get:

Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.4

But it hangs here, apparently doing nothing (no cpu is taken by the
process). This is the same whatever application using gtk I launch.
Something which may be of some interest is that when I launches an
application with GTK_IM_MODULE set to scim under strace, it always hangs
at the following call:

connect(3, {sa_family=AF_FILE, path="/tmp/scim-socket-frontend-david"},

Sometimes, it does launch, but when I try to input some japanese, it
hangs up again (on the same call if I run the application under strace).
I don't know if this is related, but as this cause many problems for
other softwares: I have my home on a NFS share,

Cheers,

David