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

[Bug] [Quattro]: Interrupted thumbnail generation can permanently hide wallpapers

Reported by AksharP5 · filed Aug 12, 2026Closed upstream on 2026-08-13 by the merge of PR #6775 (closed by dhh). GitHub close reason: completed.

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

[Bug] [Quattro]: Interrupted thumbnail generation can permanently hide wallpapersrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 4.0.0.r1688.g438f7b3-1 (Quattro), kernel 7.1.8-arch1-3

What's wrong?

If thumbnail generation from #6686 is interrupted, .jpg.lock directories can remain. The next run drops thumbnails blocked by those locks, then caches the incomplete rows with valid directory signatures. Later picker opens reuse that partial cache indefinitely.

Reproduce:
1. Start the background picker with several uncached images.
2. Stop it while vipsthumbnail workers are running.
3. Open the picker again.

Expected: every image is retried and shown.

Actual: only thumbnails completed before interruption are shown. In one occurrence, four locks were created together but only one thumbnail completed. Every source image generated successfully after clearing the stale cache; there was no OOM or decode failure.

View raw text
### System details

Omarchy 4.0.0.r1688.g438f7b3-1 (Quattro), kernel 7.1.8-arch1-3

### What's wrong?

If thumbnail generation from #6686 is interrupted, `.jpg.lock` directories can remain. The next run drops thumbnails blocked by those locks, then caches the incomplete rows with valid directory signatures. Later picker opens reuse that partial cache indefinitely.

Reproduce:
1. Start the background picker with several uncached images.
2. Stop it while `vipsthumbnail` workers are running.
3. Open the picker again.

Expected: every image is retried and shown.

Actual: only thumbnails completed before interruption are shown. In one occurrence, four locks were created together but only one thumbnail completed. Every source image generated successfully after clearing the stale cache; there was no OOM or decode failure.

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.