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.
Wallpaper intermittently turns black and workspace switching feels slow
Reported by felixzsh · filed Oct 3, 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
Summary
On my laptop, the wallpaper intermittently disappears to black and reappears, especially while switching workspaces. Workspace switching also feels unusually slow during the same period. This began after powering on the laptop. The issue was actively occurring while I reported it, but I am updating the system now, so the observations below are only from before that update; I have not gathered any post-update findings.
System observed
- Omarchy theme: Catppuccin
- Display: one built-in eDP-1 panel, 2560x1440, Intel UHD Graphics 620
- Configured background:
~/.config/omarchy/backgrounds/catppuccin/armored-girl.png; the file exists andomarchy theme bg currentreportedArmored Girl. - The running Quickshell process was launched from
/home/felix/Work/open-source/omarchy/shell(local checkout), rather than a packaged shell path. Please note this may affect reproducibility.
Relevant logs
The user wallpaper daemon was active, but repeatedly logged:
shell background enable failed: omarchy-shell is not responding
shell handoff failed, keeping the renderer for the still
shell background disable failed: omarchy-shell is not respondingAt startup it also logged omarchy-shell is not running, followed by an owe-render socket never appeared / renderer start failed message. A later renderer did start successfully. Quickshell logs showed repeated QLocalSocket::PeerClosedError warnings.
Expected
The wallpaper should remain visible, and switching workspaces should be responsive.
Actual
The wallpaper alternates between visible and black, and workspace switching feels slow. The logs suggest a possible issue handing off wallpaper rendering between owed and omarchy-shell, but I cannot confirm the root cause.
The session was in the middle of a system update when this issue was filed; these details describe the state before the update/restart.
View raw text
## Summary On my laptop, the wallpaper intermittently disappears to black and reappears, especially while switching workspaces. Workspace switching also feels unusually slow during the same period. This began after powering on the laptop. The issue was actively occurring while I reported it, but I am updating the system now, so the observations below are only from before that update; I have not gathered any post-update findings. ## System observed - Omarchy theme: Catppuccin - Display: one built-in eDP-1 panel, 2560x1440, Intel UHD Graphics 620 - Configured background: `~/.config/omarchy/backgrounds/catppuccin/armored-girl.png`; the file exists and `omarchy theme bg current` reported `Armored Girl`. - The running Quickshell process was launched from `/home/felix/Work/open-source/omarchy/shell` (local checkout), rather than a packaged shell path. Please note this may affect reproducibility. ## Relevant logs The user wallpaper daemon was active, but repeatedly logged: ```text shell background enable failed: omarchy-shell is not responding shell handoff failed, keeping the renderer for the still shell background disable failed: omarchy-shell is not responding ``` At startup it also logged `omarchy-shell is not running`, followed by an `owe-render socket never appeared` / `renderer start failed` message. A later renderer did start successfully. Quickshell logs showed repeated `QLocalSocket::PeerClosedError` warnings. ## Expected The wallpaper should remain visible, and switching workspaces should be responsive. ## Actual The wallpaper alternates between visible and black, and workspace switching feels slow. The logs suggest a possible issue handing off wallpaper rendering between `owed` and `omarchy-shell`, but I cannot confirm the root cause. The session was in the middle of a system update when this issue was filed; these details describe the state before the update/restart.
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 21:00 UTC