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

Ghostty screensaver config uses removed key background-color (Ghostty 1.x)

Reported by DarkestFog · filed Oct 8, 2026 · open at source

Decided: Out of scope — decided by agents · verified 2 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

Ghostty screensaver config uses removed key background-color (Ghostty 1.x)revision 1 · captured 2026-10-08 10:44 UTC via poll

What happened

Launching the Omarchy screensaver with Ghostty as the default terminal prints:

/usr/share/omarchy/default/ghostty/screensaver:5:background-color: unknown field

What was expected

The screensaver terminal launches without config warnings and with the intended black background.

Steps to reproduce

  1. Omarchy 4.0.4-1, Ghostty 1.3.1-arch2, default terminal = Ghostty (xdg-terminal-exec --print-id -> com.mitchellh.ghostty.desktop)
  2. omarchy launch screensaver (or wait for idle screensaver)

Cause

Ghostty 1.x renamed the config key background-color to background. Omarchy still ships the old key in /usr/share/omarchy/default/ghostty/screensaver:

window-padding-x = 0
window-padding-y = 0
window-padding-color = "extend-always"
font-family = "JetBrainsMono Nerd Font"
background-color = "#000000"

The fix is renaming line 5 to background = "#000000".

Impact

Non-fatal: the warning is printed and the black background is not applied (falls back to the active theme's terminal background, e.g. #0B0C16).

System details

  • Omarchy: 4.0.4-1
  • Ghostty: 1.3.1-arch2
  • Full diagnostics: generated by omarchy-debug --no-sudo --print (see /tmp/omarchy-debug.log)
View raw text
## What happened

Launching the Omarchy screensaver with Ghostty as the default terminal prints:

```
/usr/share/omarchy/default/ghostty/screensaver:5:background-color: unknown field
```

## What was expected

The screensaver terminal launches without config warnings and with the intended black background.

## Steps to reproduce

1. Omarchy 4.0.4-1, Ghostty 1.3.1-arch2, default terminal = Ghostty (`xdg-terminal-exec --print-id` -> `com.mitchellh.ghostty.desktop`)
2. `omarchy launch screensaver` (or wait for idle screensaver)

## Cause

Ghostty 1.x renamed the config key `background-color` to `background`. Omarchy still ships the old key in `/usr/share/omarchy/default/ghostty/screensaver`:

```ini
window-padding-x = 0
window-padding-y = 0
window-padding-color = "extend-always"
font-family = "JetBrainsMono Nerd Font"
background-color = "#000000"
```

The fix is renaming line 5 to `background = "#000000"`.

## Impact

Non-fatal: the warning is printed and the black background is not applied (falls back to the active theme's terminal background, e.g. #0B0C16).

## System details

- Omarchy: 4.0.4-1
- Ghostty: 1.3.1-arch2
- Full diagnostics: generated by `omarchy-debug --no-sudo --print` (see /tmp/omarchy-debug.log)

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 22:48 UTC