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

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

Use Super + Space → Install → Package, or install each package explicitly:

omarchy pkg add fcitx5
omarchy pkg add fcitx5-configtool
omarchy pkg add fcitx5-chinese-addons
omarchy pkg add fcitx5-rime
omarchy pkg add noto-fonts-cjk

Chinese Addons is enough for common Pinyin; add fcitx5-rime for Rime. Verify names through the menu or official Arch package search when they change, and never substitute Ubuntu apt commands.

Official links: Fcitx 5, Rime, Noto CJK, and Nerd Fonts. They cover the input framework, input schema, CJK glyph coverage, and terminal icon glyphs respectively; do not treat all four as one configuration problem.

Start Fcitx5 and add a method

Start it manually, prove the process exists, and open configuration:

fcitx5 -d
pgrep -a fcitx5
fcitx5-configtool

Then:

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

If Fcitx5 does not start after logging in again, launch it once from the application menu and inspect the session's autostart settings. Do not start fcitx5 -d from several startup files at once.

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.

If you also need per-device or per-application XKB switching, review the community Keyboard Layout Switcher. It manages keyboard layouts rather than Chinese input methods; avoid letting it, the first-party widget, keyd, and legacy Omakeyd rules compete for the same keys.

Configure Rime and double pinyin

Make the default Rime schema work before adding a third-party schema, double-pinyin layout, or synchronized dictionary. The Fcitx5 Rime user directory is normally ~/.local/share/fcitx5/rime. Back it up before editing:

mkdir -p ~/.local/share/fcitx5
if [ -d ~/.local/share/fcitx5/rime ]; then
  cp -a ~/.local/share/fcitx5/rime ~/.local/share/fcitx5/rime.backup
fi

The command skips the copy when the directory does not exist. Keep user configuration in a private backup and do not edit package-managed files under /usr/share.

A recoverable workflow is:

1. Back up the current Rime user directory.
2. Add one schema or patch at a time.
3. Redeploy Rime.
4. Test both a normal text field and a terminal.
5. 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 controls the main monospaced choice, while CJK prose still depends on fontconfig fallback. Refresh and inspect matches after installation:

fc-cache -fv
fc-match sans-serif:lang=zh-cn
fc-match monospace:lang=zh-cn
fc-list :lang=zh family | sort -u | head -30

Then 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

Create a diagnostic report first:

fcitx5-diagnose > ~/fcitx5-diagnose.txt

It can contain session paths and environment details, so redact before sharing.

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.