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

Menu is black after Qt 6.12.0 / quickshell 0.3.2 upgrade (Color singleton sub-objects undefined)

Reported by thesteganos · filed Oct 8, 2026 · open at source

Partly in the audited area (menu) — decided by agents · verified. Not validated 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?
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?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. So far: partly in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Menu is black after Qt 6.12.0 / quickshell 0.3.2 upgrade (Color singleton sub-objects undefined)revision 1 · captured 2026-10-08 22:53 UTC via poll

Summary

After upgrading to Qt 6.12.0, Super + Space opens the Omarchy menu as a fully black screen. The shell's Color singleton sub-objects (Color.menu, Color.tooltip, Color.bar, ...) evaluate to undefined, so every themed surface (menu, tooltips, OSD, buttons) gets no colors.

System

  • Omarchy 4.0.4-1, Hyprland 0.56.2, kernel 7.2.8-5-omarchy-bore
  • Lenovo YOGA 510-14ISK, Intel i7-6500U (Skylake iGPU), 1366x768
  • Upgraded the same day: 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-1, quickshell 0.3.1-1 -> 0.3.2-1
  • Theme: sunset (custom theme under ~/.config/omarchy/themes)

Steps to reproduce

  1. Update to qt6 6.12.0 + quickshell 0.3.2.
  2. Press Super + Space (or run omarchy-menu toggle).
  3. hyprctl layers shows the omarchy-menu layer at full size, but the screen is black.

Log (qs log -p /usr/share/omarchy/shell)

@plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor
@Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefined
plugins/menu/Menu.qml[87:-1]: TypeError: Cannot read property 'background' of undefined
plugins/menu/Menu.qml[91:-1]: TypeError: Cannot read property 'scrim' of undefined
@Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined

Errors are present from shell startup (before the menu is opened), and affect the bar, OSD, reminders, and Ui/* controls too.

Ruled out

  • ~/.config/omarchy/shell.toml override (removed it: same errors)
  • QML disk cache (~/.cache/quickshell/qmlcache removed: same errors)
  • omarchy restart shell
  • pacman -Qkk omarchy: no modified files; theme colors.toml and shell.toml in ~/.local/state/omarchy/current/theme are valid

Suspected cause

Behavior change in Qt 6.12 around pragma Singleton / readonly property QtObject in shell/Commons/Color.qml. Not confirmed; I did not downgrade Qt.

Full omarchy debug output available on request.

View raw text
## Summary
After upgrading to Qt 6.12.0, `Super + Space` opens the Omarchy menu as a fully black screen. The shell's `Color` singleton sub-objects (`Color.menu`, `Color.tooltip`, `Color.bar`, ...) evaluate to `undefined`, so every themed surface (menu, tooltips, OSD, buttons) gets no colors.

## System
- Omarchy 4.0.4-1, Hyprland 0.56.2, kernel 7.2.8-5-omarchy-bore
- Lenovo YOGA 510-14ISK, Intel i7-6500U (Skylake iGPU), 1366x768
- Upgraded the same day: 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-1, quickshell 0.3.1-1 -> 0.3.2-1
- Theme: sunset (custom theme under ~/.config/omarchy/themes)

## Steps to reproduce
1. Update to qt6 6.12.0 + quickshell 0.3.2.
2. Press Super + Space (or run `omarchy-menu toggle`).
3. `hyprctl layers` shows the `omarchy-menu` layer at full size, but the screen is black.

## Log (`qs log -p /usr/share/omarchy/shell`)
```
@plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor
@Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefined
plugins/menu/Menu.qml[87:-1]: TypeError: Cannot read property 'background' of undefined
plugins/menu/Menu.qml[91:-1]: TypeError: Cannot read property 'scrim' of undefined
@Commons/Border.qml[25:-1]: TypeError: Cannot read property 'menu.border-alpha' of undefined
```
Errors are present from shell startup (before the menu is opened), and affect the bar, OSD, reminders, and Ui/* controls too.

## Ruled out
- `~/.config/omarchy/shell.toml` override (removed it: same errors)
- QML disk cache (`~/.cache/quickshell/qmlcache` removed: same errors)
- `omarchy restart shell`
- `pacman -Qkk omarchy`: no modified files; theme `colors.toml` and `shell.toml` in `~/.local/state/omarchy/current/theme` are valid

## Suspected cause
Behavior change in Qt 6.12 around `pragma Singleton` / `readonly property QtObject` in `shell/Commons/Color.qml`. Not confirmed; I did not downgrade Qt.

Full `omarchy debug` output available on request.

Also reported as

This defect is tracked under R-5254 (filed Oct 8, 2026). 16 other reports describe the same defect.

Earliest report of this defect: R-5253 (filed Oct 8, 2026). Upstream consolidates it in R-5327 (other reports were closed there as its duplicates).

  1. Oct 8, 2026R-5254 · this report— tracked here
  2. ·Decided by agents · verified

    Open upstream.

  3. ·Decided by agents · verified

    Open upstream.

  4. ·Decided by agents · verified

    Open upstream.

  5. ·Decided by arbitration

    Open upstream.

  6. ·Decided by agents · verified

    Open upstream.

  7. ·Decided by agents · verified

    Open upstream.

  8. ·Decided by agents · verified

    Open upstream.

  9. ·Decided by agents · verified

    Open upstream.

  10. ·Decided by agents · verified

    Closed upstream on 2026-10-11 by its own reporter HVA344. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

  11. ·Decided by agents · verified

    Open upstream.

  12. ·Decided by agents · verified

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

  13. ·Decided by agents · verified

    Open upstream.

  14. ·Decided by agents · verified

    Open upstream.

  15. ·Decided by arbitration

    Open upstream.

  16. ·Decided by agents · verified

    Open upstream.

  17. ·Decided by agents · verified

    Open upstream.

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.

  • Decided by agents · verified: partly in the audited area (menu)
  • Decided by agents · verified: matches no known issue

The outcome (valid, duplicate, not a bug, …) is not decided yet.