OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
wayland-compat high occasional DISPUTE

No CJK / compose input in Electron and Chromium apps on Wayland

omarchyarchendeavouroscachyosmanjarohyprlanddesktoplaptop
CORRECTED An auditor found the fix wrong or incomplete and rewrote it.
AUDIT NOTE

The record is a faithful copy of a stale ArchWiki note and its central claim is false on the Chromium this machine runs. Checked in Chromium's own source at the exact branch of the installed build (chromium 151.0.7922.173-1, branch-heads/7922): ui/base/ui_base_features.cc declares BASE_FEATURE(kWaylandTextInputV3, base::FEATURE_ENABLED_BY_DEFAULT), and ui/ozone/platform/wayland/host/wayland_input_method_context.cc IsImeEnabled() returns true on that feature alone, so --enable-wayland-ime is NOT required. The same file picks text-input-v1 only when --enable-wayland-ime AND --wayland-text-input-version=1 are both passed, otherwise it calls EnsureTextInputV3(). So Chromium defaults to v3, not v1. I bisected the flip across branch-heads: 6998 (M134) and 6834 are FEATURE_DISABLED_BY_DEFAULT, 7103 (M136) and every branch after it are enabled. Milestone to branch mapping confirmed from chromiumdash fetch_milestones (134 -> 6998, 136 -> 7103, 151 -> 7922). Electron inherits this: releases.electronjs.org/releases.json gives electron 35 -> chromium 134.0.6998.x (still v1) and electron 36 -> chromium 136.0.7103.x (v3 by default). The ArchWiki Fcitx5 and Chromium pages still carry the old text, refetched today, so the cited sources do say what the record claims and none are removed. All four flags still exist in the installed binary (strings /usr/lib/chromium/chromium matches enable-wayland-ime, wayland-text-input-version, disable-gtk-ime, gtk-version), and the ~/.config/chromium-flags.conf mechanism is real: the launcher binary's help text names chromium-flags.conf under /etc and $XDG_CONFIG_HOME. Four Omarchy 4 specifics the record misses. (1) Omarchy already ships the IM module variables in /usr/lib/environment.d/10-omarchy-fcitx.conf, owned by omarchy-settings 4.0.2-1, setting INPUT_METHOD, QT_IM_MODULE, XMODIFIERS and SDL_IM_MODULE to fcitx. systemctl --user show-environment on this machine shows QT_IM_MODULE=fcitx, XMODIFIERS=@im=fcitx, SDL_IM_MODULE=fcitx live. (2) GTK_IM_MODULE is deliberately absent from that file, and ArchWiki Fcitx5 says IM modules should be used only for Xwayland apps, so the record's instruction to export GTK_IM_MODULE=fcitx session wide pushes native GTK Wayland apps off the text-input path they already use. (3) Omarchy runs fcitx5 itself as /usr/lib/systemd/user/omarchy-fcitx5.service (active on this machine, PID 2541), and hyprctl -j devices shows hl-virtual-keyboard-fcitx5 with main: true, so a reader here would find fcitx5 already attached and the record's pgrep -a fcitx5 step passing while telling them nothing. (4) Omarchy actively manages ~/.config/chromium-flags.conf. /usr/share/omarchy/config/chromium-flags.conf is the template and migrations 1784508556.sh, 1780517689.sh and 1785543725.sh append --password-store=gnome-libsecret and --load-extension lines to it. The record's code fence reads as 'write this file' and the per-app loop uses > which truncates, which on this workstation would have destroyed a live ~/.config/spotify-flags.conf carrying a scale fix. The fix now says append. Also corrected: electron38-flags.conf names a package that is no longer in the repos, extra ships electron, electron39, electron40, electron41, electron42 and electron43 as of today, and ArchWiki Electron records that --ozone-platform-hint=wayland was removed in Electron 38. Hyprland 0.56.2 implements both protocols: upstream src/protocols at tag v0.56.2 contains TextInputV1.cpp, TextInputV3.cpp and InputMethodV2.cpp, and the installed /usr/bin/Hyprland binary contains zwp_text_input_manager_v1 and zwp_text_input_manager_v3. hyprctl has no command to list Wayland globals, only devices and globalshortcuts, so it cannot show which text-input version a client bound. NOT exercised: I did not launch Chromium or any Electron app, did not type a CJK character, did not write any flags file, and did not read chrome://version. Every behavioural claim above comes from source at the installed version or from a local file, not from a run.

The cause above was rewritten on 2026-09-13 to match this note; the fix was corrected by the audit itself.
RISK

Do not truncate ~/.config/chromium-flags.conf on Omarchy 4. Omarchy seeds and then appends to that file through its migrations, and two of the lines it puts there matter: --password-store=gnome-libsecret pins the cookie and password encryption key, so losing it makes existing cookies and saved logins undecryptable and signs you out of everything, and a --load-extension list carries Omarchy's own browser extensions. Append with >>. The same applies to any per-application flags file you may already have. Pick one Chromium IME workaround and test it before adding another: --enable-wayland-ime, --gtk-version=4 and --disable-gtk-ime are listed on the ArchWiki Chromium page as alternatives for the same class of problem, not as a set to combine.

Symptom

Fcitx5 works fine in kitty, Firefox and native Wayland apps, but in Chromium, VS Code, Discord, Obsidian or Spotify pressing Ctrl+Space does nothing, no candidate window ever appears, and you cannot type a single Chinese, Japanese or Korean character. Dead keys and the Compose key are dead in the same apps. fcitx5-diagnose reports no problems. This is now mostly a symptom of old builds: Chromium 135 and earlier, and apps bundling Electron 35 or earlier. Chromium 136 and later, which is what Omarchy 4 ships today, speak text-input-v3 by default and do not need any flag.

Cause

Wayland IME goes through the text-input protocol, and which version a Chromium client speaks depends on its milestone. Chromium 136 and later enable the WaylandTextInputV3 feature by default: ui/base/ui_base_features.cc declares it FEATURE_ENABLED_BY_DEFAULT, and ui/ozone/platform/wayland/host/wayland_input_method_context.cc turns the Wayland IME path on from that feature alone, then binds zwp_text_input_v3. On those builds no command-line flag is needed and the protocol is already v3. Chromium 135 and earlier shipped the feature disabled, so the Wayland IME path stayed off unless --enable-wayland-ime was passed, and it then bound text-input-v1, which most compositors and toolkits do not pair with. Electron follows its bundled Chromium: Electron 35 carries Chromium 134 and has the old behaviour, Electron 36 carries Chromium 136 and has the new one.

So on Omarchy 4 with the current chromium package, a missing candidate window is usually NOT a text-input version problem any more. The remaining causes are an app bundling Electron 35 or older, a build launched under XWayland where text-input does not apply at all and the legacy XIM path is used instead, or fcitx5 not running. The ArchWiki Fcitx5 and Chromium pages still state that Chromium defaults to text-input-v1, which was true through Chromium 135 and is no longer true.

Fix

First find out whether you actually have a version problem.

**On Omarchy 4** fcitx5 is already installed, already started, and its environment variables are already set by the distribution. Check the service rather than hunting for a stray process:


systemctl --user status omarchy-fcitx5
cat /usr/lib/environment.d/10-omarchy-fcitx.conf
hyprctl -j devices | grep -i fcitx

A healthy Omarchy 4 session shows the unit active (running) and an hl-virtual-keyboard-fcitx5 entry under keyboards. On plain Arch, start fcitx5 yourself and see the existing fcitx5-cjk-input-not-working-wayland record for the daemon and environment side.

Now check the Chromium version, because that decides whether any flag is needed:


pacman -Q chromium

**Chromium 136 or newer, or Electron 36 or newer, needs no flags.** Those builds enable the WaylandTextInputV3 feature by default and bind zwp_text_input_v3 on their own. Hyprland 0.56.2 implements text-input-v1, text-input-v3 and input-method-v2, so the pair matches. If the candidate window still does not appear on such a build, the cause is elsewhere: the app is running under XWayland, or fcitx5 has no input method configured.

Find out which Electron an app bundles before deciding:


pacman -Qi <package> | grep -i depends     # names electron39, electron40, ...

Arch currently ships electron, electron39, electron40, electron41, electron42 and electron43 in extra. All of them are past Electron 36.

**Chromium 135 or older, or Electron 35 or older**, needs the flags. Arch's chromium reads one flag per line from ~/.config/chromium-flags.conf.

> On Omarchy 4 that file is not yours alone. Omarchy seeds it from /usr/share/omarchy/config/chromium-flags.conf and its migrations append lines to it, including --password-store=gnome-libsecret and a --load-extension list. Overwriting it logs you out of every site whose cookies were sealed with the gnome-libsecret key and removes Omarchy's browser extensions. **Append, never truncate.**


printf -- '--enable-wayland-ime\n--wayland-text-input-version=3\n' >> ~/.config/chromium-flags.conf

Arch's electron package reads the same style of file, preferring the versioned name and falling back to the unversioned one:


printf -- '--enable-wayland-ime\n--wayland-text-input-version=3\n' >> ~/.config/electron-flags.conf

Some apps read a per-application file named after the binary. Append to those too, and check first, because you may already have one:


for a in vesktop spotify code obsidian; do
  [ -f ~/.config/$a-flags.conf ] && cat ~/.config/$a-flags.conf
  printf -- '--enable-wayland-ime\n--wayland-text-input-version=3\n' >> ~/.config/$a-flags.conf
done

Apps that bundle their own Electron, such as discord and slack-desktop, ignore all of the above. Patch their desktop entry instead:


cp /usr/share/applications/discord.desktop ~/.local/share/applications/
sed -i 's|^Exec=/usr/bin/discord|Exec=/usr/bin/discord --enable-wayland-ime --wayland-text-input-version=3|' \
  ~/.local/share/applications/discord.desktop
update-desktop-database ~/.local/share/applications

Fully quit the app and start it again from the launcher. Do not use an in-app relaunch button, because Chromium relaunches on the old platform.

If an app is running under XWayland it needs the legacy XIM path instead, not text-input. **On Omarchy 4 this is already done**: XMODIFIERS=@im=fcitx, QT_IM_MODULE=fcitx, SDL_IM_MODULE=fcitx and INPUT_METHOD=fcitx come from /usr/lib/environment.d/10-omarchy-fcitx.conf, shipped by omarchy-settings. Confirm rather than re-adding them:


systemctl --user show-environment | grep -E 'IM_MODULE|XMODIFIERS'

Do not add GTK_IM_MODULE=fcitx. Omarchy leaves it unset on purpose, and the ArchWiki Fcitx5 page recommends IM modules only for Xwayland applications, because setting it pushes native GTK Wayland apps off the text-input path they already use.

**On plain Arch with a uwsm session**, put the Xwayland variables in a uwsm drop-in rather than in hyprland.lua:


# ~/.config/uwsm/env.d/im.conf
export XMODIFIERS=@im=fcitx
export QT_IM_MODULE=fcitx

On Omarchy 4 the equivalent user override point is a drop-in read by the systemd user manager:


# ~/.config/environment.d/im.conf
QT_IM_MODULE=fcitx

Log out and back in either way.

Verify

Open the app, press Ctrl+Space, and check the fcitx5 candidate window appears over the app window. hyprctl clients | grep -A6 <class> should show xwayland: 0 for a native Wayland Electron app, because an app on XWayland cannot use text-input at all and needs the XIM path instead. If you added flags, confirm they were read: launch the app from a terminal and check chrome://version shows them on the command line. On Chromium 136 or newer with no flags set, a working candidate window is the expected result and the absence of the flags on that command line is correct.

Sources

electron-chromium-ime-no-wayland-text-input