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.
omarchy font set prints omarchy-notification-send usage error when the font name contains a space
Reported by TheRealGhost007 · filed Sep 4, 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
What happened
$ omarchy font set "Fira Mono"
15887
Usage: omarchy-notification-send [--app-name <app-name>] [-g <glyph>] [-u <low|normal|critical>] [-i <icon>] [-t <ms>] [-r <id>] [-p] [--image <path-or-uri>] <headline> [description] [--exec <program> [args...]]
The font does get set correctly despite the error - confirmed:
$ omarchy font current
Fira Mono
So this is cosmetic, not functional, but it's a real parse/quoting bug: the
script's internal call to omarchy-notification-send isn't passing the
multi-word font name through correctly, so that one sub-call fails and
dumps its own usage text to the terminal.
What was expected
No error output - font names with spaces are common (most Google/Nerd Fonts
have them) and omarchy font list itself lists plenty, e.g. "Fira Mono",
"DM Mono", "Google Sans Code".
Steps to reproduce
omarchy font set "Fira Mono"
Single-word font names (e.g. omarchy font set FiraCode) don't show this.
System details
- Omarchy: 4.0.2-1, stable channel
- Kernel: 7.1.9-arch1-2
View raw text
### What happened
$ omarchy font set "Fira Mono"
15887
Usage: omarchy-notification-send [--app-name <app-name>] [-g <glyph>] [-u <low|normal|critical>] [-i <icon>] [-t <ms>] [-r <id>] [-p] [--image <path-or-uri>] <headline> [description] [--exec <program> [args...]]
The font *does* get set correctly despite the error - confirmed:
$ omarchy font current
Fira Mono
So this is cosmetic, not functional, but it's a real parse/quoting bug: the
script's internal call to `omarchy-notification-send` isn't passing the
multi-word font name through correctly, so that one sub-call fails and
dumps its own usage text to the terminal.
### What was expected
No error output - font names with spaces are common (most Google/Nerd Fonts
have them) and `omarchy font list` itself lists plenty, e.g. "Fira Mono",
"DM Mono", "Google Sans Code".
### Steps to reproduce
omarchy font set "Fira Mono"
Single-word font names (e.g. `omarchy font set FiraCode`) don't show this.
### System details
- Omarchy: 4.0.2-1, stable channel
- Kernel: 7.1.9-arch1-2Validation
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:46 UTC