Peter Evans <peter@despammed.com> さんは書きました:
In response to the long-suffering Mike Fabian, primarily:
In short, no change. Shift-Spacebar does nothing.
[...]
Assuming that you didn't yet edit settings for LC_CTYPE or other locale related variables to your personal profiles, I suggest that you edit /etc/sysconfig/language and use the following values:
RC_LANG="en_US.UTF-8" RC_LC_ALL="" RC_LC_MESSAGES="" RC_LC_CTYPE="ja_JP.UTF-8" RC_LC_COLLATE="" RC_LC_TIME="" RC_LC_NUMERIC="" RC_LC_MONETARY="" ROOT_USES_LANG="yes"
Done. (The previous settings were RC_LANG="en_GB", etc., so I've made some progress.)
Then run SuSEconfig and restart your X session.
SuSEconfig was another program I'd never heard of.
Often you do not need to know because YaST2 runs it automatically for you each time you install or uninstall something.
After unsuccessfully looking for it, I gave up and simply ran it at the command line.
[...]
Here's one idea. When I installed SuSE, I gratefully took the option to switch CapsLock and left-Ctrl. (I didn't ask for any other changes.) And this keyboard has a stupid Windows key (though I suppose that's common these days). Neither could have done anything to change the Shift-Space control, could it? (I wouldn't have thought so, but then I don't know what I'm doing.) More broadly, is it possible that I have Japanese input capability right now, but that it's via something other than Shift-Space? (I tried right-Shift-Space and that doesn't work either.)
It is possible to configure this and use a different keybinding than Shift-Space, but it is quite involved and I very much doubt that it is possible to do that accidentally. There is no GUI to configure this keybinding, you have to manually edit some config files. I.e. it is impossible that you did this during the installation.
Alternatively, by rebooting the computer, have I merely restarted the previous (no-Japanese-input) X window session? I'd happily restart the X session if I knew how.
Just use the logout button in the KDE start menu and then login again, that should be enough. To find out what is going wrong, please do the following: login to KDE, open a terminal and type locale What is the output? Then type echo $XMODIFIERS What is the output here? Now check whether canna is running: mike@kibou:~$ pidof cannaserver 1493 mike@kibou:~$ If canna is running, "pidof cannaserver" should return the process id, if not it returns nothing. Check whether kinput2 is running: mike@kibou:~$ pidof kinput2 1859 mike@kibou:~$ Try to get some more information about canna and it's clients: mike@kibou:~$ cannastat Connected to unix Canna Server (Ver. 3.5) Total connecting clients 2 USER_NAME ID NO U_CX C_TIME U_TIME I_TIME HOST_NAME CLIENT mike 0 0 4 Sat 17 7:58pm 13 32 127.0.0.1 kinput2 mike 12 0 3 Tue 20 1:27am 2'19 24:56 kibou(UNIX mule mike@kibou:~$ Please check and tell me what these commands return on your system. -- Mike Fabian <mfabian@suse.de> http://www.suse.de/~mfabian 睡眠不足はいい仕事の敵だ。