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

`omarchy-upgrade-to-quattro` leaves qt6-wayland dependency-marked, so the shell's Wayland platform support shows as a removable orphan

Reported by peregrinus879 · filed Aug 17, 2026 · open at source

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

`omarchy-upgrade-to-quattro` leaves qt6-wayland dependency-marked, so the shell's Wayland platform support shows as a removable orphanrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 4.0.0 (omarchy 4.0.0-1), reached via omarchy-upgrade-to-quattro on an existing pre-quattro install. Observed on an ASUS ROG Zephyrus G16 (GU605CR), but the cause is upgrade-path-generic.

What happened

After the upgrade, pacman -Qdtq lists qt6-wayland as an orphan, and pacman -Qi qt6-wayland shows Install Reason: Installed as a dependency for another package, Required By: None. The standard orphan cleanup pacman -Rns $(pacman -Qdtq) therefore removes it, and with it the Wayland platform plugin that Quickshell (the Omarchy shell) and every Qt6 app load at runtime. Qt loads platform plugins with no pacman dependency edge, so nothing in the dependency graph protects the package.

What was expected

Parity with fresh ISO installs, where qt6-wayland is provisioned through install/omarchy-other.packages and ends up explicitly installed.

Cause

omarchy-upgrade-to-quattro runs mark_packages_explicit over core_packages, the omarchy-base.packages set, the PipeWire stack, and the hardware transition packages. qt6-wayland appears only in install/omarchy-other.packages, which no pass covers, so on upgrades it arrives as a dependency of the -Syu transaction and its install reason is never aligned. The script's own audio block already states the principle this violates: "Archinstall installs the audio application during fresh ISO installs, so legacy upgrades need to ensure the same PipeWire stack is present".

Steps to reproduce

  1. Upgrade any pre-quattro install with omarchy-upgrade-to-quattro.
  2. Run pacman -Qdtq.
  3. qt6-wayland is listed; pacman -Qi qt6-wayland shows the dependency install reason.

Proposed fix

Add qt6-wayland to core_packages in omarchy-upgrade-to-quattro (installed --needed, covered by the existing mark_packages_explicit call), and optionally ship a migration that repairs already-upgraded hosts: when qt6-wayland reads as dependency-installed, run pacman -D --asexplicit qt6-wayland.

Workaround

sudo pacman -D --asexplicit qt6-wayland

View raw text
### System details

Omarchy 4.0.0 (omarchy 4.0.0-1), reached via `omarchy-upgrade-to-quattro` on an existing pre-quattro install. Observed on an ASUS ROG Zephyrus G16 (GU605CR), but the cause is upgrade-path-generic.

### What happened

After the upgrade, `pacman -Qdtq` lists `qt6-wayland` as an orphan, and `pacman -Qi qt6-wayland` shows `Install Reason: Installed as a dependency for another package`, `Required By: None`. The standard orphan cleanup `pacman -Rns $(pacman -Qdtq)` therefore removes it, and with it the Wayland platform plugin that Quickshell (the Omarchy shell) and every Qt6 app load at runtime. Qt loads platform plugins with no pacman dependency edge, so nothing in the dependency graph protects the package.

### What was expected

Parity with fresh ISO installs, where `qt6-wayland` is provisioned through `install/omarchy-other.packages` and ends up explicitly installed.

### Cause

`omarchy-upgrade-to-quattro` runs `mark_packages_explicit` over `core_packages`, the `omarchy-base.packages` set, the PipeWire stack, and the hardware transition packages. `qt6-wayland` appears only in `install/omarchy-other.packages`, which no pass covers, so on upgrades it arrives as a dependency of the `-Syu` transaction and its install reason is never aligned. The script's own audio block already states the principle this violates: "Archinstall installs the audio application during fresh ISO installs, so legacy upgrades need to ensure the same PipeWire stack is present".

### Steps to reproduce

1. Upgrade any pre-quattro install with `omarchy-upgrade-to-quattro`.
2. Run `pacman -Qdtq`.
3. `qt6-wayland` is listed; `pacman -Qi qt6-wayland` shows the dependency install reason.

### Proposed fix

Add `qt6-wayland` to `core_packages` in `omarchy-upgrade-to-quattro` (installed `--needed`, covered by the existing `mark_packages_explicit` call), and optionally ship a migration that repairs already-upgraded hosts: when `qt6-wayland` reads as dependency-installed, run `pacman -D --asexplicit qt6-wayland`.

### Workaround

`sudo pacman -D --asexplicit qt6-wayland`

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 04:39 UTC