Hey — bug report for IDA Pro 9.5 on Linux (KDE Plasma Wayland, fcitx5): CJK input is completely broken out of the box. Root cause: the bundled Qt is a private build with a renamed C++ namespace (symbols are _ZN2QT…@Qt_6, i.e. namespace QT instead of Qt), so no system-built Qt input-context plugin can ever load into the process. Meanwhile bin/plugins/platforminputcontexts/ only ships compose and ibus plugins — there’s no fcitx one — so with the standard QT_IM_MODULE=fcitx that distros export, Qt fails to find a matching plugin and silently falls back to compose, which means no fcitx at all. Note the same happens for anyone on ibus-free fcitx setups, which is the majority of Chinese/Japanese/Korean Linux users. Workaround I’m using: launch with env -u QT_IM_MODULE -u GTK_IMODULE (typo: GTK_IM_MODULE), which lets the bundled Qt Wayland client take the native zwp_text_input protocol path (KWin → input-method-v2 → fcitx5) and everything works, no plugin needed. Suggested fixes: either ship a fcitx5 platforminputcontext plugin built against the private Qt (as you already do for ibus), or make the Wayland path prefer the native text-input protocol when the requested IM plugin can’t be loaded, instead of silently degrading to compose. Happy to provide traces (QT_DEBUG_PLUGINS=1 output, nm evidence of the namespace mismatch) if useful.