(Please keep [EMAIL PROTECTED] cc:ed to help BTS tracking, thanks.)

On Wed, Oct 19, 2005 at 10:36:53AM -0300, Aaron Small wrote:
> Hi,

Hi Aaron,

Thanks for the additional information.

> Here's the module list:
> 
[list snipped]

The modules look quite fine.

> Now that you mention it, I did compile libscim8 too, I just wasn't
> looking for it and didn't notice, so didn't install it :)

And I see that your scim-modules-socket is the official version as well.
Just a reminder, that libscim8, scim-modules-socket and
scim-gtk2-immodule are all built from the same source package.

> My environment variables are the recommended values,
> XMODIFIERS="@im=SCIM" and GTK_IM_MODULE="scim", but it may be worth
> noting that I had scim held at version 1.0.2-3 before and just got
> 1.4.1-1 last night. This new version isn't working for me yet, and I
> haven't had time to look into why. Maybe related and maybe not, but I'll
> try to figure that out tonight.

Since you also have scim-pinyin (scim-chinese) installed, and the new
scim-pinyin just entered unstable yesterday, it is quite understandable.
Now that I can't reproduce this bug, but I am getting gedit to segfault
when setting GTK_IM_MODULE="scim".  So would you please test with
GTK_IM_MODULE="xim" again?  Note that if you want to have scim working,
you need to manually start it with "scim -d" (if you use
GTK_IM_MODULE="scim", scim will automatically start).  If setting
GTK_IM_MODULE to xim solves your segfault, then it may be related to
#323216 (although I doubt it).

Ming
2005.10.19


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to