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: restart notification fails (-g has no glyph) and pgrep prints PIDs
Reported by rmsturge · filed Oct 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
System details
- Omarchy: 4.0.4-1 (the same code is still on the default
quattrobranch) - Machine: Dell XPS 13 (DX13260), Intel Core 5 320, Intel Graphics
Description
omarchy font set <font> is meant to show "You must restart Foot/Ghostty to see font
change" when those terminals are running, but the notification never appears. Instead
the command prints omarchy-notification-send's usage message.
In bin/omarchy-font-set, both calls pass -g without a glyph:
if pgrep -x ghostty; then
omarchy-notification-send -g "You must restart Ghostty to see font change"
fi
if pgrep -x foot; then
omarchy-notification-send -g "You must restart Foot to see font change"
fi-g takes a value, so the message is consumed as the glyph and there's no headline left,
which makes omarchy-notification-send print its usage and exit. (It looks like the
glyph character between -g and the message was lost: note the double space.)
A smaller side effect in the same lines: pgrep -x foot / pgrep -x ghostty aren't
silenced, so the terminal's PID is printed to stdout during omarchy font set.
Steps to reproduce
- Have a foot (or ghostty) window open.
- Run
omarchy font set "JetBrainsMono Nerd Font"(any installed font).
Expected: a notification saying to restart Foot/Ghostty.
Actual: no notification; the output shows a PID followed byUsage: omarchy-notification-send [--app-name <app-name>] [-g <glyph>] ....
The font change itself still works.
Suggested fix
Restore a glyph after -g (or drop -g), and silence pgrep:
-if pgrep -x ghostty; then
- omarchy-notification-send -g "You must restart Ghostty to see font change"
+if pgrep -x ghostty >/dev/null; then
+ omarchy-notification-send "You must restart Ghostty to see font change"
fi
-if pgrep -x foot; then
- omarchy-notification-send -g "You must restart Foot to see font change"
+if pgrep -x foot >/dev/null; then
+ omarchy-notification-send "You must restart Foot to see font change"
fiView raw text
### System details - Omarchy: 4.0.4-1 (the same code is still on the default `quattro` branch) - Machine: Dell XPS 13 (DX13260), Intel Core 5 320, Intel Graphics ### Description `omarchy font set <font>` is meant to show "You must restart Foot/Ghostty to see font change" when those terminals are running, but the notification never appears. Instead the command prints `omarchy-notification-send`'s usage message. In `bin/omarchy-font-set`, both calls pass `-g` without a glyph: ```bash if pgrep -x ghostty; then omarchy-notification-send -g "You must restart Ghostty to see font change" fi if pgrep -x foot; then omarchy-notification-send -g "You must restart Foot to see font change" fi ``` `-g` takes a value, so the message is consumed as the glyph and there's no headline left, which makes `omarchy-notification-send` print its usage and exit. (It looks like the glyph character between `-g` and the message was lost: note the double space.) A smaller side effect in the same lines: `pgrep -x foot` / `pgrep -x ghostty` aren't silenced, so the terminal's PID is printed to stdout during `omarchy font set`. ### Steps to reproduce 1. Have a foot (or ghostty) window open. 2. Run `omarchy font set "JetBrainsMono Nerd Font"` (any installed font). **Expected:** a notification saying to restart Foot/Ghostty. **Actual:** no notification; the output shows a PID followed by `Usage: omarchy-notification-send [--app-name <app-name>] [-g <glyph>] ...`. The font change itself still works. ### Suggested fix Restore a glyph after `-g` (or drop `-g`), and silence `pgrep`: ```diff -if pgrep -x ghostty; then - omarchy-notification-send -g "You must restart Ghostty to see font change" +if pgrep -x ghostty >/dev/null; then + omarchy-notification-send "You must restart Ghostty to see font change" fi -if pgrep -x foot; then - omarchy-notification-send -g "You must restart Foot to see font change" +if pgrep -x foot >/dev/null; then + omarchy-notification-send "You must restart Foot to see font change" fi ```
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 21:13 UTC