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` leaves `bold_font`/`italic_font` stale in kitty.conf — bold text renders the old font
Reported by ekollof · filed Aug 30, 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
AMD Ryzen AI 9 HX 370 w/ Radeon 890M (GPD G1628-04 laptop), Omarchy 4.0.1-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2
What's wrong?
omarchy font set "<font>" updated font_family in ~/.config/kitty/kitty.conf but left the explicit bold_font <old-font> line untouched, so bold text in kitty kept rendering with the previous font (in my case Spleen16 Nerd Font). The same command correctly updated alacritty (all face lines match family = "..."), ghostty and foot — kitty is the only managed terminal with separate config lines per face.
Steps to reproduce:
- Have an explicit
bold_font SomeOtherFontline in~/.config/kitty/kitty.conf(left over from a previous font choice or manual edit) - Run
omarchy font set <new-font> grep -E "font_family|bold_font" ~/.config/kitty/kitty.conf—font_familychanged,bold_fontstill the old font- Bold text in kitty renders with the old font
Root cause in omarchy-font-set:
sed -i "s/^font_family .*/font_family $font_name/g" ~/.config/kitty/kitty.confSuggested fix — also rewrite the other face lines (leaving auto values alone, since kitty derives those from font_family):
sed -i "s/^font_family .*/font_family $font_name/g" ~/.config/kitty/kitty.conf
grep -qE '^bold_font auto$' ~/.config/kitty/kitty.conf || sed -i "s/^bold_font .*/bold_font $font_name/" ~/.config/kitty/kitty.confHappy to send a PR if you'd like. Full omarchy debug --no-sudo --print log available on request.
View raw text
**System details** AMD Ryzen AI 9 HX 370 w/ Radeon 890M (GPD G1628-04 laptop), Omarchy 4.0.1-1, Hyprland 0.56.2, kernel 7.1.9-arch1-2 **What's wrong?** `omarchy font set "<font>"` updated `font_family` in `~/.config/kitty/kitty.conf` but left the explicit `bold_font <old-font>` line untouched, so bold text in kitty kept rendering with the previous font (in my case `Spleen16 Nerd Font`). The same command correctly updated alacritty (all face lines match `family = "..."`), ghostty and foot — kitty is the only managed terminal with separate config lines per face. Steps to reproduce: 1. Have an explicit `bold_font SomeOtherFont` line in `~/.config/kitty/kitty.conf` (left over from a previous font choice or manual edit) 2. Run `omarchy font set <new-font>` 3. `grep -E "font_family|bold_font" ~/.config/kitty/kitty.conf` — `font_family` changed, `bold_font` still the old font 4. Bold text in kitty renders with the old font Root cause in `omarchy-font-set`: ```bash sed -i "s/^font_family .*/font_family $font_name/g" ~/.config/kitty/kitty.conf ``` Suggested fix — also rewrite the other face lines (leaving `auto` values alone, since kitty derives those from `font_family`): ```bash sed -i "s/^font_family .*/font_family $font_name/g" ~/.config/kitty/kitty.conf grep -qE '^bold_font auto$' ~/.config/kitty/kitty.conf || sed -i "s/^bold_font .*/bold_font $font_name/" ~/.config/kitty/kitty.conf ``` Happy to send a PR if you'd like. Full `omarchy debug --no-sudo --print` log available on request.
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 10:08 UTC