IBus (Intelligent Input Bus) is an input method framework, a type of application that allows for easily switching between different keyboard layouts. When combined with an input method editor, it also allows for typing non-Latin characters using a keyboard that does not natively support them.
Additionally, see Input method#List of available input method editors for a comprehensive list of available input method editors.
Set at least the following environment variables:
GTK_IM_MODULE=ibus QT_IM_MODULE=ibus XMODIFIERS=@im=ibus
To launch IBus on user login, create an autostart entry with the following command:
On the next login IBus will start along with the user session.
- KDE comes with a plasmoid called Input Method Panel that can act as an IBus frontend and can possibly provide a better integrated experience. To launch IBus with Input Method Panel, use the
--panel=/usr/lib/kimpanel-ibus-paneloption with the ibus-daemon command above. To configure the Input Method Panel widget, see the KDE UserBase Wiki and KDE#Widgets for details.
- Additional functionality on KDE may be provided by . However, the project has been archived and may not work as expected.
See Locale for help with adding non-Latin language support to your system.
See Fonts#Non-latin scripts for a non-exhaustive list of available non-Latin fonts.
GNOME uses IBus by default, so you can simply go to System Settings → Region & Language and add a keyboard layout for the language of your choice.
Other desktop environments
To launch the IBus preferences window, you can:
- Right-click on its tray icon and select Preferences, or
- Find and launch the GUI application IBus Preferences, or
- Run the command
ibus-setupin a terminal
The points of interest here are the keyboard shortcut for Next input method (which is the one you will want to use instead of the default shortcut provided by your desktop environment) and the Input Method tab where you can add or remove the different keyboard layouts (which is where you will want to do this instead of your desktop environment's default layout manager).
Tips and tricks
IBus supports the input of emoji icons. Type
<Ctrl>+<Shift>+e and you will see the input prompt change to an underlined e character. You can then type the symbol or name of the emoji you want (e.g. :) or face) and press
<Space> to render it. If you are satisfied with the result press
<Enter> to submit it and exit emoji input mode, or press
<Space> for a second time to open a dialog where you can further customize your desired emoji.
IBus supports the input of complex Unicode characters. Type
<Ctrl>+<Shift>+u and you will see the input prompt change to an underlined u character. You can then type the code of the Unicode character you want and press
<Enter> to render and submit it.
Tray icon color
By default, IBus uses a dark blue color to display the language symbol of the currently active layout (e.g. EN). The color value is stored in a gsettings schema, so if you wish to change it you can run the following command:
$ gsettings set org.freedesktop.ibus.panel xkb-icon-rgba 'COLOR'
The string 'COLOR' should conform to the following guidelines:
The RGBA value can be 1. a color name from X11, 2. a hex value in form '#rrggbb' where 'r', 'g' and 'b' are hex digits of the red, green, and blue, 3. a RGB color in form 'rgb(r,g,b)' or 4. a RGBA color in form 'rgba(r,g,b,a)' where 'r', 'g', and 'b' are either integers in the range 0 to 255 or percentage values in the range 0% to 100%, and 'a' is a floating point value in the range 0 to 1 of the alpha.
Layout switcher display delay
When pressing the Next input method hotkey, IBus displays a small dialog to signify the layout switch. By default this dialog is displayed 400ms after pressing the key, but this value can be changed by the user, with some interesting choices being '0' to display the dialog immediately without any delay, or a negative value (e.g. '-1') to switch the layouts without showing the window at all (which may be useful if you only use two layouts and simply switch from one to the other).
The value is stored in a gsettings schema, so if you wish to change it you can run the following command:
$ gsettings set org.freedesktop.ibus.general switcher-delay-time 'VALUE'
To show the currently stored value, run the following command:
$ gsettings get org.freedesktop.ibus.general switcher-delay-time
The string 'VALUE' should conform to the following guidelines:
Set popup delay milliseconds to show IME switcher window. The default is 400. 0 = Show the window immediately. 0 < Delay milliseconds. 0 > Do not show the window and switch prev/next engines.
Using modifier key combinations to switch layouts
While it is possible to set the layout switching hotkey to a combination of only modifier keys (e.g.
<Ctrl>+<Space>, for some reason the IBus preferences GUI will not let you use a subset of modifier key combinations (e.g.
<Alt>+<Shift_R>). However, IBus stores the hotkey as a string in a gsettings schema, so you can still use such combinations by directly editing that string. To do so you can run the following command:
$ gsettings set org.freedesktop.ibus.general.hotkey triggers ['VALUE']
The string 'VALUE' should be any valid modifier key combination written in a format that IBus recognizes, e.g.
Sandboxed programs may not work with some IBus input methods due to the input socket being invisible to the sandbox. For example, Firefox sandboxed with Firejail may not register inputs given by IBus Anthy.
export GTK_IM_MODULE=xim export XMODIFIERS=@im=ibus export QT_IM_MODULE=xim
For rxvt-unicode to work correctly with IBus, you may need to add the following lines to
URxvt.inputMethod: ibus URxvt.preeditType: OverTheSpot
Missing packages due to pyenv
pyenv to manage python versions and configuration,
ibus dependencies may not be installed on the set global python version. This can happen if the global version is not the one managed by the system (to which dependencies that ibus depends on, such as
gi are installed). This may result in a running but non-functional ibus setup (ibus is in the system tray, but preferences can not be opened, etc). One way to verify this issue is to attempt to run
ibus-setup and see if any missing dependency errors arise.
To fix this issue, change your pyenv global version to the system version:
pyenv global system