## Problem

Since v3.4.0 introduced `Ctrl+Space` as the default tmux prefix, users who have **fcitx5** installed will find that the keybinding switches keyboard language instead of reaching tmux.

## Why it happens

fcitx5 (an input method framework) intercepts `Ctrl+Space` system-wide by default — it's hardcoded in `~/.config/fcitx5/config` under `[Hotkey/TriggerKeys]`. It grabs the key at the compositor level before any application (including tmux) receives it.

fcitx5 may be present on Omarchy systems even if the user never intentionally set it up, as it can be installed as a dependency.

## Fix

Remove `Control+space` from fcitx5's trigger keys in `~/.config/fcitx5/config`:

```ini
[Hotkey/TriggerKeys]
# remove the Control+space line, keep the rest:
0=Zenkaku_Hankaku
1=Hangul
```

Then restart fcitx5:

```bash
pkill fcitx5 && fcitx5 -d
```

## Suggested Omarchy-side fix

- Add a note to the tmux docs / release notes mentioning this conflict, or
- Have the Omarchy tmux setup detect and disable the fcitx5 `Ctrl+Space` binding automatically (e.g. as part of a migration or install script)
---

*edit*  I created this to check for binding conflicts in case it helps anyone: https://github.com/hoornet/keybind-audit