Proof Portal

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-4857GitHub issuePublicReceived

omarchy font set resets foot's font size to a hardcoded 9pt, desyncing it from omarchy display text size

Reported by 77-223255 · filed Sep 3, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #6957 (R-1841). GitHub close reason: completed.

Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

omarchy font set resets foot's font size to a hardcoded 9pt, desyncing it from omarchy display text sizerevision 1 · captured 2026-10-04 12:10 UTC via poll

System details: Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.11-arch1-1, Intel Raptor Lake-P / Iris Xe (Lenovo), 32 GiB RAM, SDDM. Full debug log: /tmp/omarchy-debug.log (excerpt below).

What's wrong?

omarchy font set <family> silently resets only the foot terminal's font size to a hardcoded 9pt, breaking the three-way sync that omarchy display text size maintains (shell base-size ↔ GTK text-scaling-factor ↔ terminal point size, where terminal pt = px × 9/12).

For alacritty/kitty/ghostty the command edits only the font family and leaves the size alone, but the foot branch rewrites the whole font line with a hardcoded :size=9:

# /usr/share/omarchy/bin/omarchy-font-set, line 44
if [[ -f ~/.config/foot/foot.ini ]]; then
  sed -i "s/^font=.*/font=$font_name:size=9/g" ~/.config/foot/foot.ini
fi

Steps to reproduce

  1. omarchy display text size 16 → all terminal configs get 12pt (16×9/12); foot.ini reads font=JetBrainsMono Nerd Font:size=12; everything in sync.
  2. omarchy font set "CaskaydiaMono Nerd Font" → ghostty stays 12pt, foot drops to `:size=9`. Mixed sizes across terminals.
  3. Re-running omarchy display text size 16 re-syncs all four — confirming only the font-set path corrupts foot's size.

Expected: changing the font family must not touch the font size on any terminal (same as the other three terminals).

Evidence — the command's sed behavior against the current synced configs (all four at 11pt after omarchy display text size 14):

$ echo 'font=JetBrainsMono Nerd Font:size=11' | sed 's/^font=.*/font=CaskaydiaMono Nerd Font:size=9/g'
font=CaskaydiaMono Nerd Font:size=9        # ← foot: size clobbered to 9

alacritty: size = 11                        # untouched
kitty:     font_size 11.0                   # untouched
ghostty:   font-size = 11                   # untouched

Workaround: re-run omarchy display text size <n> after every omarchy font set (this could just be chained into the font-set path).


Debug log excerpt:

Hostname: omarchy
Omarchy Package: omarchy 4.0.2-1
Kernel: 7.1.11-arch1-1 arch x86_64
Desktop: Hyprland v 0.56.2, DM: SDDM
CPU: Intel Raptor Lake-P, 12 cores / 16 threads
Device-1: Intel Raptor Lake-P [Iris Xe Graphics], vendor Lenovo
Memory: 32 GiB
View raw text
**System details**: Omarchy 4.0.2-1, Hyprland 0.56.2, kernel 7.1.11-arch1-1, Intel Raptor Lake-P / Iris Xe (Lenovo), 32 GiB RAM, SDDM. Full debug log: `/tmp/omarchy-debug.log` (excerpt below).

**What's wrong?**

`omarchy font set <family>` silently resets **only** the foot terminal's font size to a hardcoded 9pt, breaking the three-way sync that `omarchy display text size` maintains (shell `base-size` ↔ GTK `text-scaling-factor` ↔ terminal point size, where terminal pt = px × 9/12).

For alacritty/kitty/ghostty the command edits only the font family and leaves the size alone, but the foot branch rewrites the whole font line with a hardcoded `:size=9`:

```bash
# /usr/share/omarchy/bin/omarchy-font-set, line 44
if [[ -f ~/.config/foot/foot.ini ]]; then
  sed -i "s/^font=.*/font=$font_name:size=9/g" ~/.config/foot/foot.ini
fi
```

**Steps to reproduce**

1. `omarchy display text size 16` → all terminal configs get 12pt (16×9/12); foot.ini reads `font=JetBrainsMono Nerd Font:size=12`; everything in sync.
2. `omarchy font set "CaskaydiaMono Nerd Font"` → ghostty stays 12pt, **foot drops to `:size=9`**. Mixed sizes across terminals.
3. Re-running `omarchy display text size 16` re-syncs all four — confirming only the font-set path corrupts foot's size.

**Expected**: changing the font family must not touch the font size on any terminal (same as the other three terminals).

**Evidence** — the command's sed behavior against the current synced configs (all four at 11pt after `omarchy display text size 14`):

```
$ echo 'font=JetBrainsMono Nerd Font:size=11' | sed 's/^font=.*/font=CaskaydiaMono Nerd Font:size=9/g'
font=CaskaydiaMono Nerd Font:size=9        # ← foot: size clobbered to 9

alacritty: size = 11                        # untouched
kitty:     font_size 11.0                   # untouched
ghostty:   font-size = 11                   # untouched
```

**Workaround**: re-run `omarchy display text size <n>` after every `omarchy font set` (this could just be chained into the font-set path).

---

Debug log excerpt:

```
Hostname: omarchy
Omarchy Package: omarchy 4.0.2-1
Kernel: 7.1.11-arch1-1 arch x86_64
Desktop: Hyprland v 0.56.2, DM: SDDM
CPU: Intel Raptor Lake-P, 12 cores / 16 threads
Device-1: Intel Raptor Lake-P [Iris Xe Graphics], vendor Lenovo
Memory: 32 GiB
```

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.

No decision has been recorded yet.