Difference between revisions of "FAQ"

From Fcitx
Jump to navigation Jump to search
(Created page with "<languages /> <translate> When you want to complain about input method cannot work correctly, please read this first. [[Special:MyLanguage/Hall of Shame for Linux IME Suppor...")
 
 
(51 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<languages />
+
<languages/>
 +
<translate>
  
<translate>
+
<!--T:1-->
 
When you want to complain about input method cannot work correctly, please read this first.
 
When you want to complain about input method cannot work correctly, please read this first.
  
 +
<!--T:72-->
 +
Since 4.2.7, fcitx provides a command called fcitx-diagnose, it will try to detect some common problem and give some advice.
 +
 +
<!--T:2-->
 
[[Special:MyLanguage/Hall of Shame for Linux IME Support|Hall of Shame for Linux IME Support]]
 
[[Special:MyLanguage/Hall of Shame for Linux IME Support|Hall of Shame for Linux IME Support]]
  
== FAQ ==
+
== When use Ctrl + Space, Fcitx cannot be triggered on == <!--T:3-->
=== When use Ctrl + Space, Fcitx cannot be triggered on ===
+
 
1. Check the application you want to type.
+
<!--T:37-->
* Is it only one app have problem?
+
Check the application you want to type.
 +
 
 +
=== Only one specific app has problem? === <!--T:61-->
 +
* The most possible reason for this is Ctrl+Space occupied by some hotkey, please change to another trigger key and try again. This usually happens in some editor, since many ide use Ctrl+Space as default key binding for Completion.
 +
 
 +
=== All Gtk Apps have problem? === <!--T:62-->
 +
* Please open a traditional Gtk App (traditional Gtk App means, it cannot be Firefox, Libreoffice, which only use Gtk as a UI style). Gedit is a good choice. Right click at the input box, there will be a menu named "Input Method", please make sure there is "Fcitx" in it and being choosed.
 +
 
 +
<!--T:63-->
 +
* If there is "Fcitx", but it still not works. Please try to restart Fcitx, if it will works at this time, please check your DBus settings, or make Fcitx start later. You can read [[Special:MyLanguage/Configure (Other)|Configure (Other)]] if you're using a custom startup script.
 +
 
 +
<!--T:64-->
 +
* If there is Fcitx but not being choosed by default, and please select it and you can immediately try again in this app. If not works, please read the entry above. For permanent fix (To use Fcitx by default), please read Configure part in [[Special:MyLanguage/Install And Configure|Install And Configure]].
 +
 
 +
<!--T:65-->
 +
* If there is no Fcitx, you should check your install first. Usually, the package name contains fcitx and gtk. If you [[Special:MyLanguage/Compile from source|compile fcitx from source]], please make sure you have enable GTK{2,3}_IM_MODULE option. If you're sure about this, please read [[Special:MyLanguage/Input method related environment variables|Input method related environment variables]] for how to update some cached file for gtk.
 +
 
 +
<!--T:38-->
 +
* If you are using Ubuntu and upgrade to 12.04 recently, or something werid happens to your system (Due to packager careless, or buggy package manager which can not do upgrade in correct order, for example, [https://bugs.archlinux.org/task/32764 pacman]), you might notice that gtk.immodules related files doesn't generate correctly during upgrade. Try uninstall {{package ubuntu|fcitx-frontend-gtk2}}, {{package ubuntu|fcitx-frontend-gtk3}} or coressponding package on your system and re-install them to trigger the file generate. Then recheck the input method menu to see whether it have "Fcitx" in the menu or not.
 +
 
 +
=== All Qt Apps have problem? === <!--T:66-->
 +
* Run qtconfig (might have different name on your distribution, it might be qtconfig-qt4), and go to the third tab, make sure fcitx is in the "Default Input Method" combo-box. If not, please check your install.
 +
* Above solution can also applies if you want use XIM, but still we highly recommend you to use im module. See Also [[Special:MyLanguage/Input method related environment variables|Input method related environment variables]].
 +
 
 +
=== Is it Java, Xterm, wine, or some other non-Gtk/Qt Application? === <!--T:39-->
 +
There are also some very rare case, that you're using a embedded linux or mini-linux distro, in which you must use XIM, the X server might missing some locale file. The file is usually needed to be under /usr/share/X11/locale/.
 +
 
 +
<!--T:40-->
 +
And When you must use XIM, please make sure, your locale '''must NOT''' be C or POSIX and need to be a valid locale (no matter which language), and need to be generated if you are using glibc (locale-gen). When you are using im module, there is no such limitation.
 +
 
 +
=== Is it a Qt application that bundles its own Qt library? === <!--T:74-->
 +
Bundled Qt library usually uses theirs own plugin directory, which is different from system's Qt. And commonly, they are also using Qt different on system Qt, which will also make it incompatible if you simply copy the system fcitx-qt files. But anyway, you can start to check whether it loads your copied files with following environment variable. Depending on how the XIM application is written, it may need to find specific font to make it work. On Archlinux xorg-mkfontscale is required to generate correct font dir files. After install it, you'll need to restart X Server to make it work.
 +
 
 +
<!--T:75-->
 +
QT_DEBUG_PLUGINS=1 QT_LOGGING_RULES="*.debug=true"
 +
 
 +
<!--T:76-->
 +
And try to resolve all incompatible errors. Usually, ubuntu's fcitx-frontend-qt5 and libfcitxqt5-1 are good source for fcitx-qt5 build against specific qt version. For example, DraftSight 2017S0 [https://groups.google.com/forum/#!topic/fcitx/9e4TI39_4sk] may work with xenial's fcitx-qt5.
  
** The most possible reason for this is Ctrl+Space occupied by some hotkey, please change to another trigger key and try again.
+
=== Emacs === <!--T:67-->
 +
Try
  
* Is it all Gtk App have problem?
+
<!--T:68-->
 +
LC_CTYPE=zh_CN.UTF-8 emacs
  
** Please open a traditional Gtk App (traditional means, it cannot be Firefox, Libreoffice, which only use Gtk as a UI style). Gedit is a good choice. Right click at the input box, there will be a menu named "Input Method", please make sure there is "Fcitx" in it and being choosed.
+
<!--T:69-->
 +
Don't forget to check your locale -a contains that. See also [[Special:MyLanguage/Input method related environment variables|Input method related environment variables]].
  
** If there is "Fcitx", but it still not works. Please try to restart Fcitx, if it will works at this time, please check your DBus settings, or make Fcitx start later. You can read [[Special:MyLanguage/Configure (Other)|Configure (Other)]] if you're using a custom startup script.
+
<!--T:70-->
 +
Emacs will use `-*-*-*-r-normal--<some font size>-*-*-*-*-*-*-*' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).  
  
** If there is Fcitx but not being choosed by default, and please select it and you can immediately try again in this app. If not works, please read the entry above. For permanent fix (To use Fcitx by default), please read Configure part in [[Special:MyLanguage/Beginner's Guide|Beginner's Guide]].
+
== Candidate window is blinking under wayland with Fcitx 5 ==
 +
This is mainly due to the whole poor state of wayland input method. The existing wayland input method protocol is not widely supported by compositor. Even though fcitx 5 support those protocols, the poor support in application and compositor make them not usable. Not to mention certain design flaw within the protocol.
  
** If there is no Fcitx, you should check your install first. Usually, the package name contains fcitx and gtk. If you compile fcitx from source, please make sure you have enable GTK{2,3}_IM_MODULE option. If you're sure about this, please read [[Special:MyLanguage/Input method related environment variables|Input method related environment variables]] for how to update some cached file for gtk.
+
In order to make input method some what usable with '''CURRENTLY''' available and widely adopted techniques, Fcitx 5 implements a mechanism called "Client Side Input Panel", which basically asks client application to render the input window. This is done through dbus and IM Module for Gtk/Qt. The implementation requires using a underlying wayland protocol xdg_popup to show the window. Unfortunately, only new version of xdg_popup protocol supports '''moving''' a visible popup window, and this part is '''NOT''' implemented in Gtk3 and Qt5. What makes it even worse is that Gtk3 and Qt5 both comes to their end of life, which means it is not possible to get this new protocol support in Gtk3/Qt5. The issue is that input method requires to display a window that resizes and moves extremely frequently. To mitigate this issue, Fcitx 5 IM Module implement a hack that when we need to move the window, it will hide the window first and then show the window. Unfortunately, this would cause certain-level of blinking. It might looks bad in certain hardware and compositor combination.
  
* Is it all Qt App have problem?
+
Here is some possible workaround for this.
** Run qtconfig (might have different name on your distribution), and go to the third tab, make sure fcitx is in the "Default Input Method" combo-box. If not, please check your install.
 
  
* Above solution can be also applied if you want use XIM, but still we highly recommend you to use im module.
+
1. Use kimpanel under GNOME shell, which will make the candidate window to be rendered with a totally different mechanism, which won't cause any blinking.  
  
* See Also [[Special:MyLanguage/Input method related environment variables|Input method related environment variables]]
+
2. Disable Fade-in and Fade-Out effect under KWin. KWin seems to tolerate such blink much better than certain compositor.
  
 +
== Problem in Firefox and Google Docs == <!--T:4-->
  
=== Problem in Firefox and Google Docs ===
+
<!--T:41-->
 
You might want to toggle preedit off temporarily, which is Ctrl+Alt+P.
 
You might want to toggle preedit off temporarily, which is Ctrl+Alt+P.
  
=== Cannot use Fcitx in flash ===
+
== Cannot use Fcitx in flash == <!--T:5-->
 +
 
 +
<!--T:42-->
 
Please read [[Special:MyLanguage/Hall of Shame for Linux IME Support|Hall of Shame for Linux IME Support]], and use im module.
 
Please read [[Special:MyLanguage/Hall of Shame for Linux IME Support|Hall of Shame for Linux IME Support]], and use im module.
  
=== [[Special:MyLanguage/ClassicUI|Classic UI]] is not transparent ===
+
== Cannot type English after updating to fcitx newer than 4.2.4 == <!--T:6-->
 +
 
 +
<!--T:43-->
 +
Make sure you have add "[[Special:myLanguage/Keyboard|Keyboard]]" to the input method list. You can use [[Special:myLanguage/Integrate with Desktop#Configuration tool|Configuration tool]].
 +
 
 +
<!--T:44-->
 +
And you may want to move "Keyboard" to the first one.
 +
 
 +
== Unexpected keyboard layout change == <!--T:7-->
 +
 
 +
<!--T:45-->
 +
Use [[Special:myLanguage/Integrate with Desktop#Configuration tool|Configuration tool]], to bind specific keyboard layout to the specific input method.
 +
 
 +
== xmodmap settings being overwritten == <!--T:8-->
 +
 
 +
<!--T:46-->
 +
Fcitx now control keyboard layout and when switch layout, xmodmap setting will be overwritten. So fcitx-xkb provides an option to specify the xmodmap script and let fcitx loads it for you whenever keyboard layout changes. Or disable fcitx-xkb addon is also a solution for you, or if your requirement is simply, for example, switching Caps Lock and Esc, which is provided by xkb option, you can just set it with your desktop keyboard configuration tool (Gnome and KDE all support such configuration).
 +
 
 +
<!--T:47-->
 +
For more detailed explanation, xmodmap is a very low level tool, that doesn't aware keyboard layout. For X11, keyboard layout is built on a set of profile, when such profile is loaded, anything you changed with xmodmap will be overwritten, this isn't specific to fcitx, but all tool that support keyboard layout configuration. Xkb option is a set of profile that can do some pre-defined change over keyboard layout, including many thing that people usually do with xmodmap, for example, defining where dead key is, switching Caps Lock and Esc, and so on. Unless you have special requirements, xkb layout and xkb option is recommended.
 +
 
 +
<!--T:71-->
 +
Since 4.2.7, Fcitx will try to load ~/.Xmodmap if it exists.
 +
 
 +
== Configure user interface, font, vertical list == <!--T:9-->
 +
 
 +
<!--T:48-->
 +
Use [[Special:myLanguage/Integrate with Desktop#Configuration tool|Configuration tool]], Addon Configuration -> Classic UI.
 +
 
 +
<!--T:49-->
 +
If you are using [[Special:myLanguage/Configtool|fcitx-configtool]] newer than 0.4.5 or [[Special:myLanguage/Kcm|kcm-fcitx]] newer 0.4.1, you can directly configure those from the first level tab.
 +
 
 +
== Possible issue for GNOME 3.6 == <!--T:10-->
 +
 
 +
<!--T:50-->
 +
[[Note for GNOME Later than 3.6]]
 +
 
 +
== [[Special:MyLanguage/ClassicUI|Classic UI]] is not transparent == <!--T:11-->
 +
 
 +
* This problem might NOT exist any more since 4.2.6 with a different approach for detect composite manager.
 
* Restart Fcitx first, if it's ok then, it might be a bug in your Window manager. Gnome-Shell, xcompmgr is known to have this bug. You can try to set the delay start to walkaround this problem.
 
* Restart Fcitx first, if it's ok then, it might be a bug in your Window manager. Gnome-Shell, xcompmgr is known to have this bug. You can try to set the delay start to walkaround this problem.
 +
* If restart Fcitx doesn't solve this problem, you should check whether your window manager supports composite or it's enabled or not.
 +
=== Kwin === <!--T:51-->
  
* If restart Fcitx doesn't solve this problem, you should check whether your window manager supports composite or it's enabled or not.
 
==== Kwin ====
 
 
Enable desktop effects.
 
Enable desktop effects.
==== Metacity before GNOME3 ====
+
=== Metacity before GNOME3 === <!--T:52-->
 +
 
 
gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true
 
gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true
==== Xfce ====
+
=== Xfce === <!--T:53-->
 +
 
 
Xfwm support composite, but need to be enabled by hand.
 
Xfwm support composite, but need to be enabled by hand.
==== Compiz ====
+
=== Compiz === <!--T:54-->
 +
 
 
0.9 series compiz can disable composite. You can use ccsm to configure it.
 
0.9 series compiz can disable composite. You can use ccsm to configure it.
==== Other window manager ====
+
=== Other window manager === <!--T:55-->
 +
 
 +
<!--T:56-->
 
You can use xcompmgr, cairo-compmgr as composite manager for them.
 
You can use xcompmgr, cairo-compmgr as composite manager for them.
  
 +
== Minecraft == <!--T:12-->
 +
 +
<!--T:34-->
 +
Original Minecraft under linux doesn't support input method, what make it worse is, XIM will conflict with its key event processing, one way to work around is, set a wrong environment variable on purpose for minecraft, then start up it. You can use following script to do that
 +
 +
<!--T:35-->
 +
<pre>#!/bin/sh
 +
# set a wrong one
 +
export XMODIFIERS="@im=null"
 +
# start minecraft, this might change depends on you're mod, but simply its what you ARE using to start minecraft.
 +
java -Xmx1024M -Xms512M -cp minecraft.jar net.minecraft.LauncherFrame</pre>
 +
 +
<!--T:58-->
 +
This way can be also used, if you don't want fcitx to work on some application which is using XIM.
 +
 +
<!--T:73-->
 +
There is a mod can be used to support input under Linux, called [http://forum.minecraftuser.jp/viewtopic.php?t=6279 NihongoMOD], 1.2.2 with minecraft 1.5.2 can work with Fcitx without upper hack.
 +
 +
== Root application under normal user X == <!--T:57-->
 +
Root application under X normal user session is always broken (in general, not specific to fcitx), due to the fact that dbus is a user session only process. The only way to type in root application with normal fcitx is to use XIM, set GTK_IM_MODULE=xim and QT_IM_MODULE=xim before you start your application.
 +
 +
== Cursor Following problem == <!--T:13-->
 +
There is a common misunderstanding that it's input method's fault that input window could not follow the cursor, which is simply wrong. This is how cursor following works: Application send the position to Input method, then input method move the input window. So if application do not send the position, the position would be wrong. This behavior is controlled by application, but not input method. So if you meet any problem, please ask application to fix it, don't ask input method to do anything. Actually, input method could do nothing with this.
 +
 +
<!--T:59-->
 +
Although there is some walkaround for specific problem, bug is still in application, not in input method.
 +
 +
<!--T:60-->
 +
* Opera, enable on the spot for [[Special:MyLanguage/XIM|XIM]].
 +
* Firefox, enable preedit.
 +
 +
<!--T:14-->
 
[[Category:How-to]]
 
[[Category:How-to]]
  
 
</translate>
 
</translate>

Latest revision as of 18:09, 10 November 2021

Other languages:
English • ‎中文(简体)‎

When you want to complain about input method cannot work correctly, please read this first.

Since 4.2.7, fcitx provides a command called fcitx-diagnose, it will try to detect some common problem and give some advice.

Hall of Shame for Linux IME Support

When use Ctrl + Space, Fcitx cannot be triggered on

Check the application you want to type.

Only one specific app has problem?

  • The most possible reason for this is Ctrl+Space occupied by some hotkey, please change to another trigger key and try again. This usually happens in some editor, since many ide use Ctrl+Space as default key binding for Completion.

All Gtk Apps have problem?

  • Please open a traditional Gtk App (traditional Gtk App means, it cannot be Firefox, Libreoffice, which only use Gtk as a UI style). Gedit is a good choice. Right click at the input box, there will be a menu named "Input Method", please make sure there is "Fcitx" in it and being choosed.
  • If there is "Fcitx", but it still not works. Please try to restart Fcitx, if it will works at this time, please check your DBus settings, or make Fcitx start later. You can read Configure (Other) if you're using a custom startup script.
  • If there is Fcitx but not being choosed by default, and please select it and you can immediately try again in this app. If not works, please read the entry above. For permanent fix (To use Fcitx by default), please read Configure part in Install And Configure.
  • If you are using Ubuntu and upgrade to 12.04 recently, or something werid happens to your system (Due to packager careless, or buggy package manager which can not do upgrade in correct order, for example, pacman), you might notice that gtk.immodules related files doesn't generate correctly during upgrade. Try uninstall fcitx-frontend-gtk2, fcitx-frontend-gtk3 or coressponding package on your system and re-install them to trigger the file generate. Then recheck the input method menu to see whether it have "Fcitx" in the menu or not.

All Qt Apps have problem?

  • Run qtconfig (might have different name on your distribution, it might be qtconfig-qt4), and go to the third tab, make sure fcitx is in the "Default Input Method" combo-box. If not, please check your install.
  • Above solution can also applies if you want use XIM, but still we highly recommend you to use im module. See Also Input method related environment variables.

Is it Java, Xterm, wine, or some other non-Gtk/Qt Application?

There are also some very rare case, that you're using a embedded linux or mini-linux distro, in which you must use XIM, the X server might missing some locale file. The file is usually needed to be under /usr/share/X11/locale/.

And When you must use XIM, please make sure, your locale must NOT be C or POSIX and need to be a valid locale (no matter which language), and need to be generated if you are using glibc (locale-gen). When you are using im module, there is no such limitation.

Is it a Qt application that bundles its own Qt library?

Bundled Qt library usually uses theirs own plugin directory, which is different from system's Qt. And commonly, they are also using Qt different on system Qt, which will also make it incompatible if you simply copy the system fcitx-qt files. But anyway, you can start to check whether it loads your copied files with following environment variable. Depending on how the XIM application is written, it may need to find specific font to make it work. On Archlinux xorg-mkfontscale is required to generate correct font dir files. After install it, you'll need to restart X Server to make it work.

QT_DEBUG_PLUGINS=1 QT_LOGGING_RULES="*.debug=true"

And try to resolve all incompatible errors. Usually, ubuntu's fcitx-frontend-qt5 and libfcitxqt5-1 are good source for fcitx-qt5 build against specific qt version. For example, DraftSight 2017S0 [1] may work with xenial's fcitx-qt5.

Emacs

Try

LC_CTYPE=zh_CN.UTF-8 emacs

Don't forget to check your locale -a contains that. See also Input method related environment variables.

Emacs will use `-*-*-*-r-normal--<some font size>-*-*-*-*-*-*-*' as basefont(in src/xfns.c), if you do not have one matched, the code for input method won't run. Install some font package may help (For required fonts xorg-fonts-misc might be the right package but you can also try other xorg-fonts-* package.).

Candidate window is blinking under wayland with Fcitx 5

This is mainly due to the whole poor state of wayland input method. The existing wayland input method protocol is not widely supported by compositor. Even though fcitx 5 support those protocols, the poor support in application and compositor make them not usable. Not to mention certain design flaw within the protocol.

In order to make input method some what usable with CURRENTLY available and widely adopted techniques, Fcitx 5 implements a mechanism called "Client Side Input Panel", which basically asks client application to render the input window. This is done through dbus and IM Module for Gtk/Qt. The implementation requires using a underlying wayland protocol xdg_popup to show the window. Unfortunately, only new version of xdg_popup protocol supports moving a visible popup window, and this part is NOT implemented in Gtk3 and Qt5. What makes it even worse is that Gtk3 and Qt5 both comes to their end of life, which means it is not possible to get this new protocol support in Gtk3/Qt5. The issue is that input method requires to display a window that resizes and moves extremely frequently. To mitigate this issue, Fcitx 5 IM Module implement a hack that when we need to move the window, it will hide the window first and then show the window. Unfortunately, this would cause certain-level of blinking. It might looks bad in certain hardware and compositor combination.

Here is some possible workaround for this.

1. Use kimpanel under GNOME shell, which will make the candidate window to be rendered with a totally different mechanism, which won't cause any blinking.

2. Disable Fade-in and Fade-Out effect under KWin. KWin seems to tolerate such blink much better than certain compositor.

Problem in Firefox and Google Docs

You might want to toggle preedit off temporarily, which is Ctrl+Alt+P.

Cannot use Fcitx in flash

Please read Hall of Shame for Linux IME Support, and use im module.

Cannot type English after updating to fcitx newer than 4.2.4

Make sure you have add "Keyboard" to the input method list. You can use Configuration tool.

And you may want to move "Keyboard" to the first one.

Unexpected keyboard layout change

Use Configuration tool, to bind specific keyboard layout to the specific input method.

xmodmap settings being overwritten

Fcitx now control keyboard layout and when switch layout, xmodmap setting will be overwritten. So fcitx-xkb provides an option to specify the xmodmap script and let fcitx loads it for you whenever keyboard layout changes. Or disable fcitx-xkb addon is also a solution for you, or if your requirement is simply, for example, switching Caps Lock and Esc, which is provided by xkb option, you can just set it with your desktop keyboard configuration tool (Gnome and KDE all support such configuration).

For more detailed explanation, xmodmap is a very low level tool, that doesn't aware keyboard layout. For X11, keyboard layout is built on a set of profile, when such profile is loaded, anything you changed with xmodmap will be overwritten, this isn't specific to fcitx, but all tool that support keyboard layout configuration. Xkb option is a set of profile that can do some pre-defined change over keyboard layout, including many thing that people usually do with xmodmap, for example, defining where dead key is, switching Caps Lock and Esc, and so on. Unless you have special requirements, xkb layout and xkb option is recommended.

Since 4.2.7, Fcitx will try to load ~/.Xmodmap if it exists.

Configure user interface, font, vertical list

Use Configuration tool, Addon Configuration -> Classic UI.

If you are using fcitx-configtool newer than 0.4.5 or kcm-fcitx newer 0.4.1, you can directly configure those from the first level tab.

Possible issue for GNOME 3.6

Note for GNOME Later than 3.6

Classic UI is not transparent

  • This problem might NOT exist any more since 4.2.6 with a different approach for detect composite manager.
  • Restart Fcitx first, if it's ok then, it might be a bug in your Window manager. Gnome-Shell, xcompmgr is known to have this bug. You can try to set the delay start to walkaround this problem.
  • If restart Fcitx doesn't solve this problem, you should check whether your window manager supports composite or it's enabled or not.

Kwin

Enable desktop effects.

Metacity before GNOME3

gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true

Xfce

Xfwm support composite, but need to be enabled by hand.

Compiz

0.9 series compiz can disable composite. You can use ccsm to configure it.

Other window manager

You can use xcompmgr, cairo-compmgr as composite manager for them.

Minecraft

Original Minecraft under linux doesn't support input method, what make it worse is, XIM will conflict with its key event processing, one way to work around is, set a wrong environment variable on purpose for minecraft, then start up it. You can use following script to do that

#!/bin/sh
# set a wrong one
export XMODIFIERS="@im=null"
# start minecraft, this might change depends on you're mod, but simply its what you ARE using to start minecraft.
java -Xmx1024M -Xms512M -cp minecraft.jar net.minecraft.LauncherFrame

This way can be also used, if you don't want fcitx to work on some application which is using XIM.

There is a mod can be used to support input under Linux, called NihongoMOD, 1.2.2 with minecraft 1.5.2 can work with Fcitx without upper hack.

Root application under normal user X

Root application under X normal user session is always broken (in general, not specific to fcitx), due to the fact that dbus is a user session only process. The only way to type in root application with normal fcitx is to use XIM, set GTK_IM_MODULE=xim and QT_IM_MODULE=xim before you start your application.

Cursor Following problem

There is a common misunderstanding that it's input method's fault that input window could not follow the cursor, which is simply wrong. This is how cursor following works: Application send the position to Input method, then input method move the input window. So if application do not send the position, the position would be wrong. This behavior is controlled by application, but not input method. So if you meet any problem, please ask application to fix it, don't ask input method to do anything. Actually, input method could do nothing with this.

Although there is some walkaround for specific problem, bug is still in application, not in input method.

  • Opera, enable on the spot for XIM.
  • Firefox, enable preedit.