Hotkeys do not work

Hi David,

By "activate from the contextual menu", do you mean the right click menu, and choose "Input Methods -> SCIM Input Method"? If so, what is chosen before you change it?

Yes, I mean the right-click menu. 'uim' was chosen before I changed it, and once I changed it Ctrl-space worked in gedit. However, it still doesn't work in Firefox.

I guess there's a preference somewhere I've set incorrectly, then.

I didn't look at UIM's im-switch setting carefully, so I don't know if this configuration is set by UIM.

But please test this, make sure you have up-to-date dapper (scim 1.4.4-1ubuntu6 is needed), and have im-switch installed, then run command "im-switch -s scim", log out of GNOME and log in again. See if everything works now.

I tried that, and it didn't fix things.

The default input method now seems to be X Input Method, but that was the case before I tried running im-switch.

This is _very_ strange. Which version is your scim? And please paste the results of following commands after running "im-switch -s scim" and logout then relogin GNOME:

locale
ls -l ~/.xinput.d
cat /etc/X11/xinit/xinput.d/scim
echo $GTK_IM_MODULE

Thanks.

OK.

scim is 1.4.4-1ubuntu6, according to synaptic.

locale gives:

LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
LC_CTYPE="en_GB.UTF-8"
LC_NUMERIC="en_GB.UTF-8"
LC_TIME="en_GB.UTF-8"
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY="en_GB.UTF-8"
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER="en_GB.UTF-8"
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT="en_GB.UTF-8"
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

ls -l ~/.xinput.d gives:

lrwxrwxrwx 1 david david 28 2006-03-24 17:37 en_GB -> /etc/X11/xinit/xinput.d/scim
lrwxrwxrwx 1 david david 28 2006-03-24 17:15 en_GB.backup -> /etc/X11/xinit/xinput.d/scim

cat /etc/X11/xinit/xinput.d/scim gives:

# im-switch configuration file for scim
# should be installed as /etc/X11/xinit/xinput.d/scim
# this configuration uses GTK IM module and Qt IM module provided by SCIM

# exported enviroment variables
XMODIFIERS="@im=SCIM"
GTK_IM_MODULE="scim"
QT_IM_MODULE="scim"
# command and arguments to invoke scim
XIM_PROGRAM="/usr/bin/scim"
XIM_ARGS="--daemon"
# package dependency (note that the format used here is not environment
# variable, but some format for libapt-pkg-perl and is parsed by grep,
# so can't be quoted, and no spaces allowed)
DEPENDS=scim-gtk2-immodule,scim-qtimm

echo #GTK_IM_MODULE gives:

[a blank line]

On Fri, Mar 24, 2006 at 08:42:37AM -0000, David Chart wrote:
>
> echo #GTK_IM_MODULE gives:
>
> [a blank line]

Hmm, I was asking for "echo $GTK_IM_MODULE", the "$" sign, not "#".

And you are using GNOME, right? How did you log into GNOME, from GDM?

Ming
2006.03.24

Oops.

echo $GTK_IM_MODULE gives:

xim

Yes, I'm using GNOME. I logged in through the GDM.

On Fri, Mar 24, 2006 at 08:56:56AM -0000, David Chart wrote:
> echo $GTK_IM_MODULE gives:
>
> xim

Thanks. This is not expected, though, so apparently something else is
interfering with the im-switch setting on your box.

> Yes, I'm using GNOME. I logged in through the GDM.

So I need some more information.

Do you have a ~/.gnomerc file? If yes, please show the contents
(command "cat ~/.gnomerc" will do). Or something like ~/.xinitrc,
~/.xsession, etc. Basically anything you did manually to start scim.

Also please show the result of "ls /etc/X11/Xsession.d" and "echo
$XMODIFIERS".

Ming
2006.03.24

.gnomerc is currently:

    XMODIFIERS="@im=SCIM"
    export XMODIFIERS
    GTK_IM_MODULE="xim"
    export GTK_IM_MODULE
    scim -d

I'll try the obvious modification and report back...

Note that this was C&P'd from one of your responses to another bug report on scim, as I was trying to fix things.

ls /etc/X11/Xsession.d is

20xorg-common_process-args 75dbus_dbus-launch
30xorg-common_xresources 90im-switch
50xorg-common_determine-startup 90xorg-common_ssh-agent
55gnome-session_gnomerc 99xorg-common_start

and echo $XMODIFIERS is

@im=SCIM

OK, replacing GTK_IM_MODULE="xim" with GTK_IM_MODULE="scim" in .gnomerc makes everything work.

The remaining question is why things didn't work to start with, since I didn't create .gnomerc until I already had a problem I was trying to fix. Still, I'm not sure how we could recover that now.

Thanks for your help.

Let's summerize:

Your settings in ~/.gnomerc is correct, and I would expect it to work. It's just overwriting the im-switch setting (which is not necessarily a bad thing). Actually I like this GTK_IM_MODULE=xim setting so much that I wrote an im-switch configuration file for it. If you use "im-switch -s scim_xim", you'll get exactly this setting as your ~/.gnomerc.

You said in the beginning of this report that your were seeing UIM in the right-click contextual menu (although you later seem to changed that), which is obviously unrelated to SCIM.

Then later you said if you run "im-switch -s scim", the contextual menu will be set to "X Input Method". According to your ~/.gnomerc setting, this is correct and expected to work. I am still curious why it didn't work, and if you are willing to continue testing, I would like to find out the reason.

In short, thing should work once you run "im-switch -s scim". After you changed you ~/.gnomerc to set GTK_IM_MODULE to scim instead of xim, things should still work, but in a different way.

Oh, I just realized one more thing:

Can you paste the result of following two commands as well?

grep "^/Supported" /etc/scim/global
grep "^/Supported" ~/.scim/global

As you are using en_GB.UTF-8 locale, that may be the reason your ~/.gnomerc setting didn't work. I never knew it only happens for XIM mode, but not GTK/Qt IM mode though.

The summary appears correct. The menu was set to uim at one point, but switched back to XIM later. I don't remember what I did in between, but I was trying a variety of input methods. The appearance of UIM is probably a red herring.

The results of the two other commands:

grep "^/Supported" /etc/scim/global:

/SupportedUnicodeLocales = en_US.UTF-8

grep "^/Supported" ~/.scim/global

[no result]

I'm happy to keep testing this until you understand the problem.

On Fri, Mar 24, 2006 at 03:02:35PM -0000, David Chart wrote:
>
> Comment:
> The summary appears correct. The menu was set to uim at one point, but
> switched back to XIM later. I don't remember what I did in between,
> but I was trying a variety of input methods. The appearance of UIM is
> probably a red herring.

Good, so it seems "im-switch -s scim" got rid of the interference of
UIM. So let's concentrate on SCIM, and I have got an idea about what
the problem is now.

> The results of the two other commands:
>
> grep "^/Supported" /etc/scim/global:
>
> /SupportedUnicodeLocales = en_US.UTF-8
>
> grep "^/Supported" ~/.scim/global
>
> [no result]

This is expected. Now please remove all your SCIM related settings in
~/.gnomerc (they are not necessary anymore now that im-switch support is
implementend), and first test "im-switch -s scim" (logout and relogin).
According to your previous comments, this is expected to work. Then run
"im-switch -s scim_xim" (logout and relogin again), and this is expected
to fail. Now please add a line
    /SupportedUnicodeLocales = en_US.UTF-8,en_GB.UTF-8
at the end of your ~/.scim/global, logout and relogin. I hope now scim
will be working.

> I'm happy to keep testing this until you understand the problem.

Thank you for the patience when I am trying to figure out the problem.
Your help is greatly appreciated.

Ming
2006.03.24

Sorry about the delay; Saturday is a busy day at work for me.

Anyway, everything happened as you said it should. GTK_IM_MODULE is now xim, but the hotkeys work to launch scim.

Thanks! Let me know if there's anything else you want me to test, but this bug is now fixed-for-me.

Just to clarify, when you say "hotkeys work to launch scim", it's after adding "/SupportedUnicodeLocales = en_US.UTF-8,en_GB.UTF-8" to ~/.scim/global, is that correct?

Right. After editing ~/.scim/global as instructed, things work, as you said they would.

David, thank you for the help on testing.

I'll close this bug now that im-switch settings are working fine.

The problem of having to add "SupportedUnicodeLocales" manually for locales other than en_US.UTF-8 is filed separately as bug #36547.