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-2096GitHub issuePublicDecided· Out of scope

omarchy-font-set: notification called with empty -g glyph, fails and skips font-set hook

Reported by ifigueroap · filed Sep 29, 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

omarchy-font-set: notification called with empty -g glyph, fails and skips font-set hookrevision 1 · captured 2026-09-29 11:20 UTC via poll

Bug

bin/omarchy-font-set passes -g without a glyph on the Ghostty/Foot restart notifications (lines 77 and 81):

omarchy-notification-send -g  "You must restart Ghostty to see font change"
omarchy-notification-send -g  "You must restart Foot to see font change"

-g consumes the message as its glyph value, leaving no headline, so omarchy-notification-send prints usage and exits 1. The notification is never shown, and because the script fails there, the final omarchy-hook font-set "$font_name" never runs.

Repro

  1. Have Ghostty (or Foot) running.
  2. Menu → Install → Style → Font → Fira Code (or run omarchy-font-set "FiraCode Nerd Font").
  3. Output ends with Usage: omarchy-notification-send ...; no notification, no font-set hook.

Fix

Supply a glyph (the glyph appears to have been lost from the source), e.g.:

omarchy-notification-send -g 󰛖 "You must restart Ghostty to see font change"
omarchy-notification-send -g 󰛖 "You must restart Foot to see font change"

Seen on omarchy 4.0.4-1; still present on main.

View raw text
## Bug

`bin/omarchy-font-set` passes `-g` without a glyph on the Ghostty/Foot restart notifications (lines 77 and 81):

```bash
omarchy-notification-send -g  "You must restart Ghostty to see font change"
omarchy-notification-send -g  "You must restart Foot to see font change"
```

`-g` consumes the message as its glyph value, leaving no headline, so `omarchy-notification-send` prints usage and exits 1. The notification is never shown, and because the script fails there, the final `omarchy-hook font-set "$font_name"` never runs.

## Repro

1. Have Ghostty (or Foot) running.
2. Menu → Install → Style → Font → Fira Code (or run `omarchy-font-set "FiraCode Nerd Font"`).
3. Output ends with `Usage: omarchy-notification-send ...`; no notification, no `font-set` hook.

## Fix

Supply a glyph (the glyph appears to have been lost from the source), e.g.:

```bash
omarchy-notification-send -g 󰛖 "You must restart Ghostty to see font change"
omarchy-notification-send -g 󰛖 "You must restart Foot to see font change"
```

Seen on omarchy 4.0.4-1; still present on `main`.

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 20:09 UTC