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.
Obsidian user-flags.conf default has single-dash typo (-disable-gpu), breaks Obsidian CLI
Reported by scossar · filed Aug 27, 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
System details
Omarchy version: 4.0.1-1, Obsidian version 1.13.7
What happened
The default ~/.config/obsidian/user-flags.conf shipped at/usr/share/omarchy/config/obsidian/user-flags.conf contains:
-disable-gpu
--enable-wayland-ime
-disable-gpu has a single dash. Electron/Chromium only recognizes---prefixed args as engine switches; a single-dash token falls through
to Obsidian's own CLI command dispatcher, which then fails to look it up
as a command. This breaks every obsidian <command> invocation, e.g.:
❯ obsidian --version
Error: Command "-disable-gpu" not found. It may require a plugin to be enabled.
Expected
The flag should be --disable-gpu (double dash), which is a valid
Chromium switch and does not interfere with Obsidian CLI command parsing.
Steps to reproduce
- Fresh Omarchy install with default
~/.config/obsidian/user-flags.conf - Run
obsidian --version(or anyobsidian <command>) from a terminal
Fix
One-character fix: change -disable-gpu to --disable-gpu inconfig/obsidian/user-flags.conf in the Omarchy repo.
System
- Omarchy version: 4.0.1-1
- Obsidian version: 1.13.7-2
Local workaround applied
Fixed ~/.config/obsidian/user-flags.conf locally: changed # -disable-gpu line to --disable-gpu.
View raw text
### System details
Omarchy version: 4.0.1-1, Obsidian version 1.13.7
## What happened
The default `~/.config/obsidian/user-flags.conf` shipped at
`/usr/share/omarchy/config/obsidian/user-flags.conf` contains:
-disable-gpu
--enable-wayland-ime
`-disable-gpu` has a single dash. Electron/Chromium only recognizes
`--`-prefixed args as engine switches; a single-dash token falls through
to Obsidian's own CLI command dispatcher, which then fails to look it up
as a command. This breaks every `obsidian <command>` invocation, e.g.:
❯ obsidian --version
Error: Command "-disable-gpu" not found. It may require a plugin to be enabled.
## Expected
The flag should be `--disable-gpu` (double dash), which is a valid
Chromium switch and does not interfere with Obsidian CLI command parsing.
## Steps to reproduce
1. Fresh Omarchy install with default `~/.config/obsidian/user-flags.conf`
2. Run `obsidian --version` (or any `obsidian <command>`) from a terminal
## Fix
One-character fix: change `-disable-gpu` to `--disable-gpu` in
`config/obsidian/user-flags.conf` in the Omarchy repo.
## System
- Omarchy version: 4.0.1-1
- Obsidian version: 1.13.7-2
## Local workaround applied
Fixed `~/.config/obsidian/user-flags.conf` locally: changed
`# -disable-gpu` line to `--disable-gpu`.
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 09:29 UTC