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 resets Foot font size to 9, ignoring omarchy display text size
Reported by sbalbalosa · filed Aug 15, 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
Summary
Changing the system font family — via the settings menu (Style → Font) or omarchy font set — silently resets Foot's font size to a hardcoded 9pt, undoing the global text size set with omarchy display text size (or the display-panel text-size slider).
Only Foot is affected. kitty, alacritty, and ghostty correctly keep their existing size when the family changes.
Steps to reproduce
omarchy display text size 16- Confirm Foot is scaled:
grep '^font=' ~/.config/foot/foot.ini→font=JetBrainsMono Nerd Font:size=12 - Change the family:
omarchy font set MesloLGLDZ Nerd Font(or the menu Style → Font picker) - Check Foot again:
grep '^font=' ~/.config/foot/foot.ini→font=MesloLGLDZ Nerd Font:size=9(size lost)
Meanwhile kitty/alacritty/ghostty remain at 12, so Foot is visibly smaller than the rest.
Expected
Only the font family changes; the :size=N chosen by omarchy display text size is preserved — same as the other three terminals.
Cause
In bin/omarchy-font-set, the Foot branch rewrites the entire font= line with a hardcoded size:
sed -i "s/^font=.*/font=$font_name:size=9/g" ~/.config/foot/foot.inikitty/alacritty/ghostty branches only rewrite their family line, so their size survives. The two font commands fight each other: picking a font in the GUI silently undoes the text-size setting.
Environment
- Omarchy 4.0.0-1 (quattro)
- Hyprland 0.56.2, Dell Latitude 5420 (Intel i5-1145G7)
- Reproduced via both CLI and the settings-menu font picker
View raw text
## Summary Changing the system font family — via the settings menu (**Style → Font**) or `omarchy font set` — silently resets **Foot's** font size to a hardcoded **9pt**, undoing the global text size set with `omarchy display text size` (or the display-panel text-size slider). Only Foot is affected. kitty, alacritty, and ghostty correctly keep their existing size when the family changes. ## Steps to reproduce 1. `omarchy display text size 16` 2. Confirm Foot is scaled: `grep '^font=' ~/.config/foot/foot.ini` → `font=JetBrainsMono Nerd Font:size=12` 3. Change the family: `omarchy font set MesloLGLDZ Nerd Font` (or the menu **Style → Font** picker) 4. Check Foot again: `grep '^font=' ~/.config/foot/foot.ini` → `font=MesloLGLDZ Nerd Font:size=9` (size lost) Meanwhile kitty/alacritty/ghostty remain at 12, so Foot is visibly smaller than the rest. ## Expected Only the font family changes; the `:size=N` chosen by `omarchy display text size` is preserved — same as the other three terminals. ## Cause In `bin/omarchy-font-set`, the Foot branch rewrites the entire `font=` line with a hardcoded size: ```bash sed -i "s/^font=.*/font=$font_name:size=9/g" ~/.config/foot/foot.ini ``` kitty/alacritty/ghostty branches only rewrite their family line, so their size survives. The two font commands fight each other: picking a font in the GUI silently undoes the text-size setting. ## Environment - Omarchy 4.0.0-1 (quattro) - Hyprland 0.56.2, Dell Latitude 5420 (Intel i5-1145G7) - Reproduced via both CLI and the settings-menu font picker
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 04:09 UTC