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

Background wallpaper renders grainy due to missing mipmaps on base Image

Reported by Carlthegreatt · filed Oct 1, 2026 · 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

Background wallpaper renders grainy due to missing mipmaps on base Imagerevision 1 · captured 2026-10-01 16:14 UTC via poll

Summary

Large, high-resolution wallpapers look grainy when set as the Omarchy background, even though the same file looks clean when opened in an image viewer. The grain is aliasing caused by downscaling the wallpaper without mipmaps.

Steps to reproduce

  1. Set a large wallpaper (e.g. 6000x3274 PNG) with omarchy theme bg set.
  2. Look at the desktop — dark/sky areas show visible fine grain.
  3. Open the same file in an image viewer — it renders clean.

Expected behavior

The background renders the same way as an image viewer: crisp, without added grain.

Actual behavior

Visible noise/grain across the wallpaper, worst in darker areas.

Root cause

In /usr/share/omarchy/shell/plugins/background/Background.qml, the main base Image (line 221) is missing smooth: true and mipmap: true, while the two transition frames (oldFrame/incomingFrame) already set both. Without mipmaps, a ~5.5x downscale (6000px -> 1080p) samples roughly one source pixel per screen pixel, aliasing fine texture into noise that reads as grain.

Measured on the affected image at 1080p: unfiltered downscale has 16.6 high-frequency stddev vs 8.5 with mipmap-quality (Lanczos) filtering.

Proposed fix

       Image {
         id: base
         anchors.fill: parent
         source: root.imageUrl(root.displayedBackground)
         fillMode: Image.PreserveAspectCrop
         asynchronous: true
         cache: true
+        smooth: true
+        mipmap: true
         onStatusChanged: {

System details

  • Omarchy: 4.0.4-1
  • GPU: Intel UHD (Alder Lake-P) + NVIDIA GeForce RTX 4050 Max-Q
  • Displays: eDP-1 1920x1080@144 (scale 1.25), HDMI-A-1 1920x1080@144
  • Affected wallpaper: 6000x3274 8-bit RGB PNG

Visual comparison

gh cannot upload media, so attach these local files from the reproduction machine (or re-create them):

  • /tmp/opencode/before-after.png — before (grainy, unfiltered) on the left, after (clean, mipmapped) on the right
  • /tmp/opencode/before-after-v.png — same, stacked vertically
View raw text
## Summary

Large, high-resolution wallpapers look **grainy when set as the Omarchy background**, even though the same file looks clean when opened in an image viewer. The grain is aliasing caused by downscaling the wallpaper without mipmaps.

## Steps to reproduce

1. Set a large wallpaper (e.g. 6000x3274 PNG) with `omarchy theme bg set`.
2. Look at the desktop — dark/sky areas show visible fine grain.
3. Open the same file in an image viewer — it renders clean.

## Expected behavior

The background renders the same way as an image viewer: crisp, without added grain.

## Actual behavior

Visible noise/grain across the wallpaper, worst in darker areas.

## Root cause

In `/usr/share/omarchy/shell/plugins/background/Background.qml`, the main `base` `Image` (line 221) is missing `smooth: true` and `mipmap: true`, while the two transition frames (`oldFrame`/`incomingFrame`) already set both. Without mipmaps, a ~5.5x downscale (6000px -> 1080p) samples roughly one source pixel per screen pixel, aliasing fine texture into noise that reads as grain.

Measured on the affected image at 1080p: unfiltered downscale has 16.6 high-frequency stddev vs 8.5 with mipmap-quality (Lanczos) filtering.

## Proposed fix

```diff
       Image {
         id: base
         anchors.fill: parent
         source: root.imageUrl(root.displayedBackground)
         fillMode: Image.PreserveAspectCrop
         asynchronous: true
         cache: true
+        smooth: true
+        mipmap: true
         onStatusChanged: {
```

## System details

- Omarchy: 4.0.4-1
- GPU: Intel UHD (Alder Lake-P) + NVIDIA GeForce RTX 4050 Max-Q
- Displays: eDP-1 1920x1080@144 (scale 1.25), HDMI-A-1 1920x1080@144
- Affected wallpaper: 6000x3274 8-bit RGB PNG

## Visual comparison

`gh` cannot upload media, so attach these local files from the reproduction machine (or re-create them):

- `/tmp/opencode/before-after.png` — before (grainy, unfiltered) on the left, after (clean, mipmapped) on the right
- `/tmp/opencode/before-after-v.png` — same, stacked vertically

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 20:29 UTC