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.
Qt 6.12 built-in QtQuick Color singleton shadows Commons/Color: whole palette undefined
Reported by AlbedoGown · filed Oct 11, 2026 · open at source
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.
- 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
After upgrading to Qt 6.12.0 the shell loses its whole palette: every Color.<surface> lookup (Color.bar, Color.menu, Color.popups, Color.tooltip, Color.polkit, Color.lock, ...) is undefined. The bar/theme colors fall back to defaults, and surfaces opened from keybindings (menu, polkit, lock, tooltips) render with no background/text, which looks like a black screen.
Cause
Qt 6.12 adds a built-in singleton QtQuick/Color (QQuickColor, exports: ["QtQuick/Color 6.12"], isSingleton: true in /usr/lib/qt6/qml/QtQuick/plugins.qmltypes). Every shell file does an unversioned import QtQuick, so the new built-in Color shadows the shell's own Commons/Color.qml singleton.
Evidence from the log after re-applying the theme:
TypeError: Property 'loadColors' of object QQuickColor(0x...) is not a functionFollowed by hundreds of:
@plugins/bar/Bar.qml: TypeError: Cannot read property 'background' of undefined
@Ui/PanelToolTip.qml: TypeError: Cannot read property 'border' of undefined
@Ui/Button.qml: Unable to assign [undefined] to QColorEnvironment
- Arch Linux ARM (aarch64),
try-omarchy-runtime 4.0.4-1 qt6-base 6.12.0-2,qt6-declarative 6.12.0-1,quickshell 0.3.2-1- Appeared after a system upgrade that moved qt6 6.11.2 -> 6.12.0 and quickshell 0.3.1 -> 0.3.2
Workaround
Pinning the QtQuick import version hides the 6.12 type:
sudo grep -rlE '^\s*import QtQuick\s*$' /usr/share/omarchy/shell \
| sudo xargs sed -i -E 's/^(\s*)import QtQuick\s*$/\1import QtQuick 6.11/'
omarchy-restart-shellAfter this the shell log is clean and the keybinding surfaces render again. User plugins with an unversioned import QtQuick need the same change.
Suggested fix
Either rename the singleton (e.g. OmarchyColor) or pin the import in the shell and document it for plugin authors. Pinning is a stopgap; Qt may keep adding types that collide with Color, Style, Border, Util.
View raw text
## Summary After upgrading to Qt 6.12.0 the shell loses its whole palette: every `Color.<surface>` lookup (`Color.bar`, `Color.menu`, `Color.popups`, `Color.tooltip`, `Color.polkit`, `Color.lock`, ...) is `undefined`. The bar/theme colors fall back to defaults, and surfaces opened from keybindings (menu, polkit, lock, tooltips) render with no background/text, which looks like a black screen. ## Cause Qt 6.12 adds a built-in singleton `QtQuick/Color` (`QQuickColor`, `exports: ["QtQuick/Color 6.12"]`, `isSingleton: true` in `/usr/lib/qt6/qml/QtQuick/plugins.qmltypes`). Every shell file does an unversioned `import QtQuick`, so the new built-in `Color` shadows the shell's own `Commons/Color.qml` singleton. Evidence from the log after re-applying the theme: ``` TypeError: Property 'loadColors' of object QQuickColor(0x...) is not a function ``` Followed by hundreds of: ``` @plugins/bar/Bar.qml: TypeError: Cannot read property 'background' of undefined @Ui/PanelToolTip.qml: TypeError: Cannot read property 'border' of undefined @Ui/Button.qml: Unable to assign [undefined] to QColor ``` ## Environment - Arch Linux ARM (aarch64), `try-omarchy-runtime 4.0.4-1` - `qt6-base 6.12.0-2`, `qt6-declarative 6.12.0-1`, `quickshell 0.3.2-1` - Appeared after a system upgrade that moved qt6 6.11.2 -> 6.12.0 and quickshell 0.3.1 -> 0.3.2 ## Workaround Pinning the QtQuick import version hides the 6.12 type: ``` sudo grep -rlE '^\s*import QtQuick\s*$' /usr/share/omarchy/shell \ | sudo xargs sed -i -E 's/^(\s*)import QtQuick\s*$/\1import QtQuick 6.11/' omarchy-restart-shell ``` After this the shell log is clean and the keybinding surfaces render again. User plugins with an unversioned `import QtQuick` need the same change. ## Suggested fix Either rename the singleton (e.g. `OmarchyColor`) or pin the import in the shell and document it for plugin authors. Pinning is a stopgap; Qt may keep adding types that collide with `Color`, `Style`, `Border`, `Util`.
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
- Duplicate ofR-5254Menu is black after Qt 6.12.0 / quickshell 0.3.2 upgrade (Color singleton sub-objects undefined)· decided by agents · verified
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.