Proof Portal

Sign in
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-2227GitHub issuePublicFixed

Theme switch keeps the previous theme's wallpaper when both themes use the same file name

Reported by kravens · filed Oct 3, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 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

Theme switch keeps the previous theme's wallpaper when both themes use the same file namerevision 1 · captured 2026-10-03 22:34 UTC via poll

System details

AMD Ryzen 9 5950X, NVIDIA RTX 5080, Omarchy quattro at 8e02fc84 (shell run from a checkout), Hyprland with two monitors.

What's wrong?

When a theme switch lands on a background whose file name the previous theme also used, the desktop goes on showing the previous theme's image after the transition.

Many stock themes ship a background with the same name and different pixels. 18 themes in themes/*/backgrounds/ each have their own omarchy.png, so switching between two of them while omarchy.png is the chosen background should hit this.

Steps

  1. Theme A and theme B each ship backgrounds/1-moon.png, with different images.
  2. With theme A applied and 1-moon.png as the background, switch to theme B.
  3. After the transition, every monitor still shows theme A's 1-moon.png.

I reproduced this by driving the background IPC the way set_theme_background does: snapshot the old and new files, background prepare, swap current/theme, then background themeTransition <old snapshot> <new snapshot> <durable path>. I used two test themes and checked the result with grim -o on each output. Switching to a background with a different file name works.

Likely cause

Both themes map to the same durable path, ~/.local/state/omarchy/current/theme/backgrounds/1-moon.png, so the base frame's path string doesn't change across the switch. BackgroundMedia caches images by URL (cached: version === 0), so even when the base frame reloads, the cached pixmap for that URL and decode size is the old theme's file. A theme switch could bump version on the base frame (the URL then carries ?v=) to make it load the new file.

Found while testing #11534 (portrait wallpaper twins), which hits the same cache for twin files that share a name across themes. That PR does not change this behaviour.

View raw text
### System details

AMD Ryzen 9 5950X, NVIDIA RTX 5080, Omarchy `quattro` at 8e02fc84 (shell run from a checkout), Hyprland with two monitors.

### What's wrong?

When a theme switch lands on a background whose file name the previous theme also used, the desktop goes on showing the previous theme's image after the transition.

Many stock themes ship a background with the same name and different pixels. 18 themes in `themes/*/backgrounds/` each have their own `omarchy.png`, so switching between two of them while `omarchy.png` is the chosen background should hit this.

**Steps**

1. Theme A and theme B each ship `backgrounds/1-moon.png`, with different images.
2. With theme A applied and `1-moon.png` as the background, switch to theme B.
3. After the transition, every monitor still shows theme A's `1-moon.png`.

I reproduced this by driving the background IPC the way `set_theme_background` does: snapshot the old and new files, `background prepare`, swap `current/theme`, then `background themeTransition <old snapshot> <new snapshot> <durable path>`. I used two test themes and checked the result with `grim -o` on each output. Switching to a background with a different file name works.

**Likely cause**

Both themes map to the same durable path, `~/.local/state/omarchy/current/theme/backgrounds/1-moon.png`, so the base frame's path string doesn't change across the switch. `BackgroundMedia` caches images by URL (`cached: version === 0`), so even when the base frame reloads, the cached pixmap for that URL and decode size is the old theme's file. A theme switch could bump `version` on the base frame (the URL then carries `?v=`) to make it load the new file.

Found while testing #11534 (portrait wallpaper twins), which hits the same cache for twin files that share a name across themes. That PR does not change this behaviour.

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/9312· 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 21:08 UTC