Chinese Input on Omarchy with Fcitx5, Rime, and CJK Fonts

Install, enable, and troubleshoot Fcitx5, Rime, Chinese input schemes, and CJK fonts on Omarchy and Wayland without breaking desktop shortcuts.

Reliable Chinese input on Omarchy requires three layers to work together: the input-method framework must be running, each application must connect to it, and the selected fonts must contain the required glyphs. Installing a Rime package alone does not fix candidate-window or missing-glyph problems.

Choose an input stack

Need	Suggested components
Pinyin, double pinyin, common Chinese methods	Fcitx5 + Chinese Addons
Rime schemas and dictionary sync	Fcitx5 + Rime
Fix CJK characters rendered as boxes	Noto CJK or Source Han fonts

Open the Omarchy menu with Super + Space, then use Install → Package to find fcitx5 and fcitx5-configtool. Add fcitx5-chinese-addons or fcitx5-rime for the desired method, and noto-fonts-cjk when CJK coverage is incomplete. Verify current names in the official Arch package search.

Review AUR sources

Dictionaries and themes not in the official repository may come from the AUR. AUR recipes are not vetted by the Arch team; inspect the PKGBUILD, source, maintenance history, and comments before installing.

Start Fcitx5 and add a method

After installation, open the Fcitx5 configuration tool:

Confirm Fcitx5 starts with the graphical session.
Add your keyboard layout and the intended Chinese method.
Choose a language toggle that does not conflict with Omarchy hotkeys.
Log out and back in so applications receive the new session environment.
Test a browser, terminal, editor, and Electron application separately.

Do not paste every environment variable from an old tutorial into every startup file. GTK, Qt, Electron, and native Wayland support changes over time. Add session variables only when a specific application fails, following the current ArchWiki Fcitx5 guide.

Configure Rime and double pinyin

Make the default Rime schema work before adding a third-party schema, double-pinyin layout, or synchronized dictionary. Keep user configuration in the Rime user directory and back it up privately instead of editing package-managed files.

A recoverable workflow is:

Back up the current Rime user directory.
Add one schema or patch at a time.
Redeploy Rime.
Test both a normal text field and a terminal.
Revert the last file when it fails instead of deleting every dictionary.

User dictionaries can contain names, addresses, and project terms. Review privacy before syncing them, and never attach the entire dictionary to a public support issue.

Set CJK fonts and fallback

Omarchy's Style → Font setting controls the main monospaced choice, while CJK prose still depends on fontconfig fallback. After adding fonts, verify:

simplified and traditional characters plus punctuation;
Nerd Font icons in the bar and terminal;
readable baselines and weights across scripts;
distinguishable full-width and half-width code characters;
expected rendering in PDFs and office files.

Do not remove system fonts to force a fallback. If priority must be fixed, create the smallest user-level fontconfig override and document why it exists.

Diagnose common failures

Symptom	Check first
No input-method icon	Whether Fcitx5 runs in this graphical session
Icon exists but no input	Method list, toggle, and application protocol support
Browser works, terminal fails	Terminal and Wayland/input-method settings
Candidate popup is misplaced	Scaling, Electron/Wayland flags, and app version
CJK glyphs are boxes	CJK package and fontconfig fallback
Update changed behavior	`.bak` user overrides and current migration notes

Next, configure display, networking, and audio. Preserve evidence and follow the troubleshooting order for system-wide failures.

Sources: ArchWiki Fcitx5, ArchWiki Fonts, and Omarchy Fonts.