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.
Applying a theme with no backgrounds/ blanks the wallpaper and leaves a dangling symlink
Reported by omarchybot · filed Aug 16, 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: Omarchy quattro @ 7488eade (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.
Applying a theme that ships no backgrounds/ directory leaves the desktop with no wallpaper and a dangling symlink, rather than keeping the previous wallpaper as the message implies.
set_theme_background at bin/omarchy-theme-set:94-100 notifies "No background was found for theme" and returns without touching current/background. That reads as "we kept what you had" — but the previous wallpaper lived at current/theme/backgrounds/<file>, inside the directory rm -rf'd and replaced at bin/omarchy-theme-set:164. So the symlink is left pointing into a directory that no longer exists.
$ omarchy theme set tokyo-night >/dev/null
$ mkdir -p ~/.config/omarchy/themes/qa-nobg
$ printf 'mode = "dark"\nbackground = "#123456"\nforeground = "#eeeeee"\n' \
> ~/.config/omarchy/themes/qa-nobg/colors.toml
$ omarchy theme set qa-nobg; echo rc=$?
rc=0
$ readlink ~/.local/state/omarchy/current/background
/home/omarchy/.local/state/omarchy/current/theme/backgrounds/1-quattro.jpg
$ readlink -f ~/.local/state/omarchy/current/background
# resolves to nothing
$ [[ -e ~/.local/state/omarchy/current/background ]] && echo yes || echo NO
NO
$ omarchy theme bg current
UnknownAll 22 shipped themes have backgrounds, so this only affects user-installed themes — reachable via omarchy theme install <git-url>, which clones and applies with no validation.
Either falling back to a solid colour from the theme's own background value, or copying the previous wallpaper forward before the rm -rf, would make the notification true.
Correction, after an independent review of this report:
Narrower than filed. A running shell keeps the wallpaper it has already loaded, so the desktop does not go blank immediately. omarchy theme bg current reports Unknown straight away, and the missing wallpaper appears on a later shell restart or recreation.
View raw text
**System details:** Omarchy `quattro` @ 7488eade (post-4.0.0), QEMU/KVM VM, Hyprland session. Found by an automated QA pass; reproduced on a disposable worker VM.
Applying a theme that ships no `backgrounds/` directory leaves the desktop with no wallpaper and a dangling symlink, rather than keeping the previous wallpaper as the message implies.
`set_theme_background` at `bin/omarchy-theme-set:94-100` notifies *"No background was found for theme"* and returns without touching `current/background`. That reads as "we kept what you had" — but the previous wallpaper lived at `current/theme/backgrounds/<file>`, inside the directory `rm -rf`'d and replaced at `bin/omarchy-theme-set:164`. So the symlink is left pointing into a directory that no longer exists.
```
$ omarchy theme set tokyo-night >/dev/null
$ mkdir -p ~/.config/omarchy/themes/qa-nobg
$ printf 'mode = "dark"\nbackground = "#123456"\nforeground = "#eeeeee"\n' \
> ~/.config/omarchy/themes/qa-nobg/colors.toml
$ omarchy theme set qa-nobg; echo rc=$?
rc=0
$ readlink ~/.local/state/omarchy/current/background
/home/omarchy/.local/state/omarchy/current/theme/backgrounds/1-quattro.jpg
$ readlink -f ~/.local/state/omarchy/current/background
# resolves to nothing
$ [[ -e ~/.local/state/omarchy/current/background ]] && echo yes || echo NO
NO
$ omarchy theme bg current
Unknown
```
All 22 shipped themes have backgrounds, so this only affects user-installed themes — reachable via `omarchy theme install <git-url>`, which clones and applies with no validation.
Either falling back to a solid colour from the theme's own `background` value, or copying the previous wallpaper forward before the `rm -rf`, would make the notification true.
---
**Correction, after an independent review of this report:**
Narrower than filed. A running shell keeps the wallpaper it has already loaded, so the desktop does not go blank immediately. `omarchy theme bg current` reports `Unknown` straight away, and the missing wallpaper appears on a later shell restart or recreation.
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
- Fixed bypr/13955· confirmed
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:24 UTC