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.
Really enjoyed reading ur blog. edbdgebbbagdfacf
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
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.
Possible issue for GNOME 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.
Enable desktop effects.
Metacity before GNOME3
gconftool-2 -s --type bool /apps/metacity/general/compositing_manager true
Xfwm support composite, but need to be enabled by hand.
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.
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.