Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
Default Voxtype type mode can corrupt longer Japanese/CJK dictation through wtype
Reported by komagata · filed Sep 3, 2026 · open at source
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
Description
Omarchy installs Voxtype with wtype and configures mode = "type" by default. In this stock configuration, longer Japanese/CJK transcriptions can arrive with missing characters, deleted preceding characters, or unintended key actions in affected applications. Switching Voxtype to mode = "paste" makes the same transcriptions arrive correctly.
All users dictating Japanese or other CJK languages with Omarchy's default Voxtype configuration are potentially affected. This is not caused by the IME itself, and it may not reproduce for every transcription or in every application: manifestation depends on the text and target application. However, ordinary Japanese sentences quickly contain enough distinct Unicode characters to reach wtype's problematic keycode positions, so this is easy to encounter in normal use.
Steps to reproduce
- Install Dictation through Omarchy.
- Set Voxtype to a multilingual model and Japanese:
[whisper]
language = "ja"- Keep Omarchy's default output configuration:
[output]
mode = "type"- Dictate a longer Japanese sentence into an affected application, such as a Chromium/Electron-based text field.
- Compare the result after changing the output mode to
paste.
Expected behavior
The default Omarchy dictation setup should insert the complete transcription without altering existing text or triggering unrelated key actions.
Actual behavior
The default direct-typing path can corrupt the transcription. Paste mode avoids the problem.
Root cause
This is not specific to Mozc. A short wtype "日本語" test succeeds in a GTK input even while Fcitx 5/Mozc is active.
The behavior instead matches upstream wtype issue https://github.com/atx/wtype/issues/71. wtype assigns unique characters to successive positions in a temporary keymap. Some clients interpret particular keycodes as conventional physical keys rather than honoring only the supplied keysym. As the number of distinct characters grows, non-ASCII characters can land on Backspace, Tab, modifier, function-key, or media-key positions.
Related upstream reports:
- https://github.com/atx/wtype/issues/31
- https://github.com/atx/wtype/issues/5
- https://github.com/peteonrails/voxtype/issues/695
Why this belongs in Omarchy too
The underlying defect is in wtype, but Omarchy selects both sides of the affected default path: its Dictation installer installs wtype and its shipped Voxtype configuration selects mode = "type". Users following the stock Omarchy flow therefore receive the affected configuration without making an explicit driver choice.
The same default-output problem and a clipboard-based proposal were previously described in Omarchy Discussion https://github.com/omacom/omarchy/discussions/7028. That discussion also explains why synthetic keyboard output is fragile for multilingual and mixed-script text.
Mitigation tradeoff
Changing Voxtype to mode = "paste" avoids the wtype text-corruption path and makes the Japanese transcription arrive correctly. However, making paste mode the Omarchy default would change behavior for every Voxtype user, including users who do not use an IME or dictate CJK text and are not currently encountering this bug.
Paste mode can replace or temporarily modify the clipboard, interact with clipboard history, fail in fields that block paste, use application-dependent paste shortcuts, and add a small delay. Therefore, a global default change is not a zero-cost fix: it trades a severe correctness problem for affected multilingual users against changed clipboard semantics for all users.
A mitigation proposal is available as draft PR https://github.com/omacom/omarchy/pull/9641. This issue tracks the user-visible bug so the project can decide whether the appropriate solution is a global paste default, a conditional fallback, a safer direct-output implementation, or an upstream fix.
Environment
Originally reproduced with:
- Omarchy: 4.0.1-1
- Voxtype: 0.7.5
- wtype: 0.4-2
- Compositor: Hyprland
- Session: Wayland
- Fcitx 5: 5.1.21-1
- Fcitx 5 Mozc: 3.34.6239.2-1
The machine is now on Omarchy 4.0.2-1 and Voxtype 1.0.0; Omarchy's shipped configuration still defaults to the same type/wtype output path.
View raw text
## Description Omarchy installs Voxtype with `wtype` and configures `mode = "type"` by default. In this stock configuration, longer Japanese/CJK transcriptions can arrive with missing characters, deleted preceding characters, or unintended key actions in affected applications. Switching Voxtype to `mode = "paste"` makes the same transcriptions arrive correctly. All users dictating Japanese or other CJK languages with Omarchy's default Voxtype configuration are potentially affected. This is not caused by the IME itself, and it may not reproduce for every transcription or in every application: manifestation depends on the text and target application. However, ordinary Japanese sentences quickly contain enough distinct Unicode characters to reach wtype's problematic keycode positions, so this is easy to encounter in normal use. ## Steps to reproduce 1. Install Dictation through Omarchy. 2. Set Voxtype to a multilingual model and Japanese: ```toml [whisper] language = "ja" ``` 3. Keep Omarchy's default output configuration: ```toml [output] mode = "type" ``` 4. Dictate a longer Japanese sentence into an affected application, such as a Chromium/Electron-based text field. 5. Compare the result after changing the output mode to `paste`. ## Expected behavior The default Omarchy dictation setup should insert the complete transcription without altering existing text or triggering unrelated key actions. ## Actual behavior The default direct-typing path can corrupt the transcription. Paste mode avoids the problem. ## Root cause This is not specific to Mozc. A short `wtype "日本語"` test succeeds in a GTK input even while Fcitx 5/Mozc is active. The behavior instead matches upstream wtype issue https://github.com/atx/wtype/issues/71. wtype assigns unique characters to successive positions in a temporary keymap. Some clients interpret particular keycodes as conventional physical keys rather than honoring only the supplied keysym. As the number of distinct characters grows, non-ASCII characters can land on Backspace, Tab, modifier, function-key, or media-key positions. Related upstream reports: - https://github.com/atx/wtype/issues/31 - https://github.com/atx/wtype/issues/5 - https://github.com/peteonrails/voxtype/issues/695 ## Why this belongs in Omarchy too The underlying defect is in wtype, but Omarchy selects both sides of the affected default path: its Dictation installer installs wtype and its shipped Voxtype configuration selects `mode = "type"`. Users following the stock Omarchy flow therefore receive the affected configuration without making an explicit driver choice. The same default-output problem and a clipboard-based proposal were previously described in Omarchy Discussion https://github.com/omacom/omarchy/discussions/7028. That discussion also explains why synthetic keyboard output is fragile for multilingual and mixed-script text. ## Mitigation tradeoff Changing Voxtype to `mode = "paste"` avoids the wtype text-corruption path and makes the Japanese transcription arrive correctly. However, making paste mode the Omarchy default would change behavior for every Voxtype user, including users who do not use an IME or dictate CJK text and are not currently encountering this bug. Paste mode can replace or temporarily modify the clipboard, interact with clipboard history, fail in fields that block paste, use application-dependent paste shortcuts, and add a small delay. Therefore, a global default change is not a zero-cost fix: it trades a severe correctness problem for affected multilingual users against changed clipboard semantics for all users. A mitigation proposal is available as draft PR https://github.com/omacom/omarchy/pull/9641. This issue tracks the user-visible bug so the project can decide whether the appropriate solution is a global paste default, a conditional fallback, a safer direct-output implementation, or an upstream fix. ## Environment Originally reproduced with: - Omarchy: 4.0.1-1 - Voxtype: 0.7.5 - wtype: 0.4-2 - Compositor: Hyprland - Session: Wayland - Fcitx 5: 5.1.21-1 - Fcitx 5 Mozc: 3.34.6239.2-1 The machine is now on Omarchy 4.0.2-1 and Voxtype 1.0.0; Omarchy's shipped configuration still defaults to the same `type`/wtype output path.
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
Not linked to any known issue, other report or change yet.
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 10:42 UTC