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-5338GitHub issuePublicDecided· Duplicate

Qt 6.12.0 breaks shell rendering: Color singleton sub-objects undefined, bar/menu invisible

Reported by dmitriy-afanasyev · filed Oct 11, 2026Closed upstream on 2026-10-12 by its own reporter dmitriy-afanasyev, as a duplicate of #14989 (R-5327). GitHub close reason: duplicate.

Decided: Duplicate — decided by agents · verified 15 h ago.

R-5254 is the earliest report of this defect — filed Oct 8, 2026, open upstream. This report (filed Oct 11, 2026) describes the same defect, so it is folded under it in the inbox.

Decided by agents · verified· Oct 11, 2026

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?
AreaPartly in the audited areamenu· 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

Qt 6.12.0 breaks shell rendering: Color singleton sub-objects undefined, bar/menu invisiblerevision 1 · captured 2026-10-11 17:31 UTC via poll

After today's system update (2026-10-11, 18:02 MSK) the shell renders transparent.

What happened

  • Bottom bar disappeared (the layer still exists in hyprctl layers — 26px at the bottom — but its content is invisible)
  • Pressing SUPER dims the screen (the menu scrim shows) but the menu itself is invisible; it still works — you can type and launch apps

Environment

  • Omarchy 4.0.4-1, Hyprland 0.56.2, Arch Linux
  • Updated packages: qt6-base 6.11.2-3 -> 6.12.0-2, qt6-declarative 6.11.2-2 -> 6.12.0-1, qt6-wayland -> 6.12.0, quickshell 0.3.1 -> 0.3.2 (plus other qt6 6.12 rebuilds)
  • omarchy package itself unchanged (4.0.4-1), theme (Lumon) and user configs untouched

Diagnostics

Mass QML errors on shell startup:

Bar.qml[81]: TypeError: Cannot read property 'active' of undefined
Bar.qml[75]: Unable to assign [undefined] to QColor
Menu.qml[87..94]: Cannot read property 'background'/'scrim'/'selectedBorder' of undefined
Commons/Border.qml[25]: Cannot read property 'menu.border-alpha' of undefined

Comparison across boots (journalctl, counting of undefined errors from omarchy-shell):

BootErrors
2026-10-09 (pre-update)0
2026-10-11 post-update718
  • Theme colors resolve correctly (omarchy theme color --all returns valid hex values)
  • Downgrading quickshell 0.3.2 → 0.3.1 did not help; it also warns: "built against Qt 6.11.2 but the system has updated to Qt 6.12.0"

Fix (local workaround)

Rolling back qt6-base to 6.11.2-3 and qt6-declarative to 6.11.2-2 restores the bar and menu immediately. This suggests a Qt 6.12 QML engine change breaks the Color singleton (Commons/Color.qml) sub-object bindings — all surface colors become undefined, so every surface renders transparent while full-screen scrims still dim the display.

View raw text
After today's system update (2026-10-11, 18:02 MSK) the shell renders transparent.

## What happened

- Bottom bar disappeared (the layer still exists in `hyprctl layers` — 26px at the bottom — but its content is invisible)
- Pressing SUPER dims the screen (the menu scrim shows) but the menu itself is invisible; it still works — you can type and launch apps

## Environment

- Omarchy 4.0.4-1, Hyprland 0.56.2, Arch Linux
- Updated packages: `qt6-base 6.11.2-3 -> 6.12.0-2`, `qt6-declarative 6.11.2-2 -> 6.12.0-1`, `qt6-wayland -> 6.12.0`, `quickshell 0.3.1 -> 0.3.2` (plus other qt6 6.12 rebuilds)
- `omarchy` package itself unchanged (4.0.4-1), theme (Lumon) and user configs untouched

## Diagnostics

Mass QML errors on shell startup:

```
Bar.qml[81]: TypeError: Cannot read property 'active' of undefined
Bar.qml[75]: Unable to assign [undefined] to QColor
Menu.qml[87..94]: Cannot read property 'background'/'scrim'/'selectedBorder' of undefined
Commons/Border.qml[25]: Cannot read property 'menu.border-alpha' of undefined
```

Comparison across boots (`journalctl`, counting `of undefined` errors from omarchy-shell):

| Boot | Errors |
|---|---|
| 2026-10-09 (pre-update) | 0 |
| 2026-10-11 post-update | 718 |

- Theme colors resolve correctly (`omarchy theme color --all` returns valid hex values)
- Downgrading quickshell 0.3.2 → 0.3.1 did **not** help; it also warns: "built against Qt 6.11.2 but the system has updated to Qt 6.12.0"

## Fix (local workaround)

Rolling back `qt6-base` to 6.11.2-3 and `qt6-declarative` to 6.11.2-2 restores the bar and menu immediately. This suggests a Qt 6.12 QML engine change breaks the `Color` singleton (`Commons/Color.qml`) sub-object bindings — all surface colors become `undefined`, so every surface renders transparent while full-screen scrims still dim the display.

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

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.

  • DuplicateR-5254Decided by agents · verified · 2026-10-11 17:43 UTC