IME Not Working with IBus

[nazdridoy]

What Operating System(s) are you seeing this problem on?

Linux X11

Which Wayland compositor or X11 Window manager(s) are you using?

X11, kwin (KDE)

WezTerm version

20240203-110809-5046fc22

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

Yes, and I updated the version box above to show the version of the nightly that I tried

Describe the bug

I recently switched from Kitty to Wezterm. Today, I discovered that my IME isn't functioning in Wezterm. I'm using the IBus input method, which appeared to work fine with Kitty.

To Reproduce

not sure

Configuration

> cat /etc/environment
QT_QPA_PLATFORMTHEME=qt5ct
BROWSER=vivaldi-stable
EDITOR=nvim
XDG_CURRENT_DESKTOP="KDE"

# Ibus KDE
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
GLFW_IM_MODULE=ibus

> sed -n '46,47p' $XDG_CONFIG_HOME/wezterm/wezterm.lua

config.use_ime = true
config.xim_im_name = "ibus"

Expected Behavior

ime should work

Logs

No response

Anything else?

No response

[pjm0616]

@nazdridoy Hi! I've encountered the same issue and made a fix that works for me. The pull request is at https://github.com/wez/xcb-imdkit-rs/pull/2, and I've also uploaded a branch with the fix applied: https://github.com/pjm0616/wezterm/tree/20240825-fix-x11-ime If you're still interested it would be nice if you could check if the fix also works for you.

[JuhoKang]

I'm having the same problem. IME not working

Pop!_OS 22.04 LTS wezterm 20240203-110809-5046fc22

[freddong]

same problem on Fedora 41 wezterm from copr 20250105_002513_8d7e899a

[koopa1338]

What is the status of this, there seems to be no progress in the PR. This is kind of annoying, at least for me in 9/10 the keyboard change isn't working. Sometimes I can get it to work by opening another terminal but this is very unreliable.

[pjm0616]

@koopa1338 Hi, can you try if this branch fixes the issue for you? Currently I'm using custom built wezterm with my fix applied.

That branch is somewhat old, but you only need to change xcb-imdkit in Cargo.toml to point to my fork of xcb-imdkit on top on the wezterm main branch if you want the latest version.

If I apply my pull request at https://github.com/wez/xcb-imdkit-rs/pull/2, wezterm IME works 100% of the time for me, but my fix is somewhat quirky and not an ideal fix. Since then I've quite been busy so I hadn't had the time to work on it.

[koopa1338]

@pjm0616 I tried the wezterm main branch with your xcb-imd-kit branch and it worked like a charm. Would be great if your PR could land in the near future, anything I could help with?

[wez]

This should be resolved now in main.

It typically takes about an hour before commits are available as nightly builds for all platforms. Linux builds are the fastest to build and are often available within about 20 minutes. Windows and macOS builds take a bit longer.

Please take a few moments to try out the fix and let me know how that works out. You can find the nightly downloads for your system in the wezterm installation docs.

If you prefer to use packages provided by your distribution or package manager of choice and don't want to replace that with a nightly download, keep in mind that you can download portable packages (eg: a .dmg file on macOS, a .zip file on Windows and an .AppImage file on Linux) that can be run without permanently installing or replacing an existing package, and can then simply be deleted once you no longer need them.

If you are eager and can build from source then you may be able to try this out more quickly.

[wez]

(Thanks to @pjm0616!)

[pjm0616]

@wez I can confirm that current wezterm main branch(474ad16eb63acae78ce8138cfce0b63d01927374, built from source) works great and have no problem with IME in my setup(Ubuntu 24.04 + X11 + ibus + awesome wm). Thanks!

[github-actions[bot]]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.