Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-2201GitHub issuePublicFixed

Guide Japanese users to fcitx5-mozc after install (docs/guidance only)

Reported by usutani · filed Oct 3, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
AreaOutside the audited area· Decided by agents · verified
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Guide Japanese users to fcitx5-mozc after install (docs/guidance only)revision 1 · captured 2026-10-03 05:01 UTC via poll

Summary

A user who selects Japanese at install gets a JIS keymap, but no path to actual Japanese (kana-kanji) input. fcitx5-mozc and fcitx5-configtool are not installed, and the only pointer is one paragraph in the manual. This proposes docs/guidance-only improvement, scoped to Japanese. No installer package changes, no system-locale changes.

Current state (verified on 4.0.4-1)

  • Installer offers Japanese|jp106 (install/provisioning/setup-form.sh:58), XKB/console layout selection only, no IME mention.
  • Base packages ship only the framework (install/omarchy-base.packages:35-37: fcitx5, fcitx5-gtk, fcitx5-qt). No fcitx5-mozc, no fcitx5-configtool.
  • omarchy-fcitx5.service is enabled for CapsLock compose (install/user/first-run/enable-user-units.sh:20), not for CJK input.
  • The only guidance is one paragraph under Keyboard, Mouse, Trackpad > Typing in Chinese, Japanese, and other languages: install e.g. fcitx5-mozc via omarchy pkg add, plus fcitx5-configtool.
  • Net effect: installable with a Japanese keyboard, but Japanese input does not work out of the box and first-time users get stuck.

Repro

  1. Fresh install, select Japanese keyboard.
  2. Log in, try kana-kanji conversion.
  3. Nothing works until the user discovers omarchy pkg add fcitx5-mozc fcitx5-configtool, adds Mozc in configtool, sets the switch key, and re-logs in.

Proposal (docs/guidance only)

  • Expand the manual section with the concrete post-install steps: omarchy pkg add fcitx5-mozc fcitx5-configtool → add Mozc in configtool → set switch key (Ctrl+Space / Zenkaku_Hankaku etc.) → re-login.
  • Optionally surface the same pointer at first boot / in Setup > Input help text so Japanese-layout users can find it.
  • Link known caveats instead of fixing them here (see below).

Non-goals (to avoid re-litigating #1187)

  • No system-locale (LANG) changes. System stays English, per DHH's stance in #1187.
  • No automatic mozc installation, no new installer options.
  • No keyboard auto-detection (separate topic, on hold).

Related issues

  • #483 (closed via #760): fcitx5 XKB override — background, already fixed.
  • #1449 (closed): fcitx5 purpose Q&A.
  • #1108 (closed): layout-name mapping (uk/gb) — same class of concern as jp106 mapping.
  • #6085 (closed via #6344): non-Latin layout usability — precedent for layout-side fixes.
  • #9552 (open, bug): fcitx5 resident breaks Hyprland multi-layout switching — linked as known caveat, not in scope.

Open question

  • What Japanese|jp106 actually writes to XKBLAYOUT (cf. the uk→gb precedent)? Worth one line in the doc fix if it turns out to be jp106 verbatim vs jp.

Environment: Omarchy 4.0.4-1, Hyprland (manual section verified at omarchy.org/manual/keyboard-mouse-trackpad/).

View raw text
## Summary

A user who selects `Japanese` at install gets a JIS keymap, but no path to actual Japanese (kana-kanji) input. `fcitx5-mozc` and `fcitx5-configtool` are not installed, and the only pointer is one paragraph in the manual. This proposes docs/guidance-only improvement, scoped to Japanese. No installer package changes, no system-locale changes.

## Current state (verified on 4.0.4-1)

- Installer offers `Japanese|jp106` (`install/provisioning/setup-form.sh:58`), XKB/console layout selection only, no IME mention.
- Base packages ship only the framework (`install/omarchy-base.packages:35-37`: `fcitx5`, `fcitx5-gtk`, `fcitx5-qt`). No `fcitx5-mozc`, no `fcitx5-configtool`.
- `omarchy-fcitx5.service` is enabled for CapsLock compose (`install/user/first-run/enable-user-units.sh:20`), not for CJK input.
- The only guidance is one paragraph under `Keyboard, Mouse, Trackpad > Typing in Chinese, Japanese, and other languages`: install e.g. `fcitx5-mozc` via `omarchy pkg add`, plus `fcitx5-configtool`.
- Net effect: installable with a Japanese keyboard, but Japanese input does not work out of the box and first-time users get stuck.

## Repro

1. Fresh install, select `Japanese` keyboard.
2. Log in, try kana-kanji conversion.
3. Nothing works until the user discovers `omarchy pkg add fcitx5-mozc fcitx5-configtool`, adds Mozc in configtool, sets the switch key, and re-logs in.

## Proposal (docs/guidance only)

- Expand the manual section with the concrete post-install steps: `omarchy pkg add fcitx5-mozc fcitx5-configtool` → add Mozc in configtool → set switch key (`Ctrl+Space` / `Zenkaku_Hankaku` etc.) → re-login.
- Optionally surface the same pointer at first boot / in `Setup > Input` help text so Japanese-layout users can find it.
- Link known caveats instead of fixing them here (see below).

## Non-goals (to avoid re-litigating #1187)

- No system-locale (`LANG`) changes. System stays English, per DHH's stance in #1187.
- No automatic `mozc` installation, no new installer options.
- No keyboard auto-detection (separate topic, on hold).

## Related issues

- #483 (closed via #760): fcitx5 XKB override — background, already fixed.
- #1449 (closed): `fcitx5` purpose Q&A.
- #1108 (closed): layout-name mapping (`uk`/`gb`) — same class of concern as `jp106` mapping.
- #6085 (closed via #6344): non-Latin layout usability — precedent for layout-side fixes.
- #9552 (open, bug): fcitx5 resident breaks Hyprland multi-layout switching — linked as known caveat, not in scope.

## Open question

- What `Japanese|jp106` actually writes to `XKBLAYOUT` (cf. the `uk`→`gb` precedent)? Worth one line in the doc fix if it turns out to be `jp106` verbatim vs `jp`.

**Environment:** Omarchy 4.0.4-1, Hyprland (manual section verified at `omarchy.org/manual/keyboard-mouse-trackpad/`).

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

  • Fixed bypr/13327· confirmed
  • Fixed bypr/9634· confirmed

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

  • Out of scopeDecided by agents · verified · 2026-10-09 20:55 UTC