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-5243GitHub issuePublicReceived

Wallpaper JPEG-to-WebP upgrade leaves current/background pointing to removed JPEG

Reported by hhdri · filed Oct 8, 2026Closed upstream on 2026-10-09 by the merge of PR #14603 (closed by emirb). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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?
Not yet mapped to any requirement or component.
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Wallpaper JPEG-to-WebP upgrade leaves current/background pointing to removed JPEGrevision 1 · captured 2026-10-08 14:44 UTC via poll

System details

Omarchy edge 4.0.0.r6807.g902fd8a-1 (commit 902fd8a), stock Tokyo Night theme. WebP image support was installed.

What's wrong?

After switching from stable to edge, updating, and rebooting, the desktop wallpaper was black. The saved wallpaper symlink still pointed to 2-swirl-buck.jpg, but the refreshed Tokyo Night theme contained 2-swirl-buck.webp instead. The image itself was present; its filename extension had changed.

This follows the bundled wallpaper conversion in Store theme backgrounds as webp (#7477).

Confirmed evidence and recovery

Before repair:

~/.local/state/omarchy/current/background
  -> ~/.local/state/omarchy/current/theme/backgrounds/2-swirl-buck.jpg

2-swirl-buck.jpg: missing
2-swirl-buck.webp: present

The shell journal reported that it could not open the missing JPEG wallpaper target.

Updating the link to the equivalent WebP restored the wallpaper, confirmed visually:

omarchy theme bg set ~/.local/state/omarchy/current/theme/backgrounds/2-swirl-buck.webp

Hyprland could render a Foot terminal. There were separate bar/theme warnings during this session; this report is specifically about the verified dangling wallpaper link and its successful repair.

Reproduction path

  1. On a version containing Tokyo Night's 2-swirl-buck.jpg, select it as the current wallpaper.
  2. Upgrade across #7477 and refresh the current theme, as happened during the stable-to-edge update here.
  3. Restart the shell or reboot.
  4. Observe that current/background still targets the removed .jpg, although the replacement .webp exists, and the wallpaper is black.

This was observed during a real upgrade. I have not repeated the full upgrade on a disposable installation.

Likely mechanism

In the installed scripts, omarchy-theme-refresh calls omarchy-theme-set with OMARCHY_THEME_SKIP_BACKGROUND=1. omarchy-theme-set replaces the staged/current theme directory, but its skip-background branch only applies the theme palette and leaves the current wallpaper link unchanged. When the selected bundled asset changes extension, the previously valid link becomes dangling.

Expected behavior / suggested fix

Preserve the selected wallpaper across bundled asset renames. During refresh or an upgrade migration, if the existing target disappeared, resolve the corresponding replacement (for this conversion, the same basename with .webp) and update the link. If no equivalent exists, choose a valid fallback rather than leaving a dangling link. Also reconcile any remembered per-theme wallpaper paths affected by the conversion, and cover an upgrade with a previously selected JPEG in a regression test.

Related: #7116 also concerns a dangling wallpaper link, but its trigger is applying a user theme with no backgrounds. Here a stock theme has the replacement image and an upgrade changes its extension.

Filed by GPT-6 via Codex.

View raw text
### System details

Omarchy edge `4.0.0.r6807.g902fd8a-1` (commit `902fd8a`), stock Tokyo Night theme. WebP image support was installed.

### What's wrong?

After switching from stable to edge, updating, and rebooting, the desktop wallpaper was black. The saved wallpaper symlink still pointed to `2-swirl-buck.jpg`, but the refreshed Tokyo Night theme contained `2-swirl-buck.webp` instead. The image itself was present; its filename extension had changed.

This follows the bundled wallpaper conversion in [Store theme backgrounds as webp (#7477)](https://github.com/omacom/omarchy/commit/a4219f8f4a13b833351e6e36510e421fd1fe8e75).

### Confirmed evidence and recovery

Before repair:

```text
~/.local/state/omarchy/current/background
  -> ~/.local/state/omarchy/current/theme/backgrounds/2-swirl-buck.jpg

2-swirl-buck.jpg: missing
2-swirl-buck.webp: present
```

The shell journal reported that it could not open the missing JPEG wallpaper target.

Updating the link to the equivalent WebP restored the wallpaper, confirmed visually:

```bash
omarchy theme bg set ~/.local/state/omarchy/current/theme/backgrounds/2-swirl-buck.webp
```

Hyprland could render a Foot terminal. There were separate bar/theme warnings during this session; this report is specifically about the verified dangling wallpaper link and its successful repair.

### Reproduction path

1. On a version containing Tokyo Night's `2-swirl-buck.jpg`, select it as the current wallpaper.
2. Upgrade across #7477 and refresh the current theme, as happened during the stable-to-edge update here.
3. Restart the shell or reboot.
4. Observe that `current/background` still targets the removed `.jpg`, although the replacement `.webp` exists, and the wallpaper is black.

This was observed during a real upgrade. I have not repeated the full upgrade on a disposable installation.

### Likely mechanism

In the installed scripts, `omarchy-theme-refresh` calls `omarchy-theme-set` with `OMARCHY_THEME_SKIP_BACKGROUND=1`. `omarchy-theme-set` replaces the staged/current theme directory, but its skip-background branch only applies the theme palette and leaves the current wallpaper link unchanged. When the selected bundled asset changes extension, the previously valid link becomes dangling.

### Expected behavior / suggested fix

Preserve the selected wallpaper across bundled asset renames. During refresh or an upgrade migration, if the existing target disappeared, resolve the corresponding replacement (for this conversion, the same basename with `.webp`) and update the link. If no equivalent exists, choose a valid fallback rather than leaving a dangling link. Also reconcile any remembered per-theme wallpaper paths affected by the conversion, and cover an upgrade with a previously selected JPEG in a regression test.

Related: #7116 also concerns a dangling wallpaper link, but its trigger is applying a user theme with no backgrounds. Here a stock theme has the replacement image and an upgrade changes its extension.

Filed by GPT-6 via Codex.

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.

No decision has been recorded yet.