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.0 update breaks the shell: quickshell 0.3.1-1 still built against Qt 6.11.2
Reported by selfcrypto · filed Oct 7, 2026Closed upstream on 2026-10-08 by the bot omarchybot. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.
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
System details
AMD Ryzen 9 5900X, NVIDIA RTX 2080 Ti, Omarchy 4.0.4
What's wrong?
Today's update pulls Qt 6.12.0 from extra, but quickshell 0.3.1-1 is still built against Qt 6.11.2. After the update and a shell restart:
- The bar is gone.
- Every menu (Super+Space, Super+Esc) blacks out the screen with nothing drawn.
Shell log:
WARN: Quickshell was built against Qt 6.11.2 but the system has updated to Qt 6.12.0 without rebuilding the package. This is likely to cause crashes, so the quickshell package must be rebuilt.
WARN scene: @plugins/bar/Bar.qml[81:-1]: TypeError: Cannot read property 'active' of undefined
WARN scene: @plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor
WARN scene: @Ui/Button.qml[57:-1]: TypeError: Cannot read property 'background' of undefined
WARN scene: @Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefinedThe same undefined theme errors show up in every plugin.
Steps:
omarchy update(Qt 6.11.2 -> 6.12.0, quickshell stays 0.3.1-1)omarchy restart shell, or reboot
Workaround: downgrade the qt6-* packages plus fcitx5-qt, python-pyqt6, qt6ct and telegram-desktop from the pacman cache, then add them to IgnorePkg until quickshell is rebuilt. The shell works again after a restart.
Upstream build fix: quickshell-mirror/quickshell#1235. Same kind of mismatch as #8438.
View raw text
### System details AMD Ryzen 9 5900X, NVIDIA RTX 2080 Ti, Omarchy 4.0.4 ### What's wrong? Today's update pulls Qt 6.12.0 from extra, but `quickshell 0.3.1-1` is still built against Qt 6.11.2. After the update and a shell restart: - The bar is gone. - Every menu (Super+Space, Super+Esc) blacks out the screen with nothing drawn. Shell log: ``` WARN: Quickshell was built against Qt 6.11.2 but the system has updated to Qt 6.12.0 without rebuilding the package. This is likely to cause crashes, so the quickshell package must be rebuilt. WARN scene: @plugins/bar/Bar.qml[81:-1]: TypeError: Cannot read property 'active' of undefined WARN scene: @plugins/bar/Bar.qml[75:3]: Unable to assign [undefined] to QColor WARN scene: @Ui/Button.qml[57:-1]: TypeError: Cannot read property 'background' of undefined WARN scene: @Ui/PanelToolTip.qml[22:-1]: TypeError: Cannot read property 'background' of undefined ``` The same `undefined` theme errors show up in every plugin. Steps: 1. `omarchy update` (Qt 6.11.2 -> 6.12.0, quickshell stays 0.3.1-1) 2. `omarchy restart shell`, or reboot Workaround: downgrade the qt6-* packages plus fcitx5-qt, python-pyqt6, qt6ct and telegram-desktop from the pacman cache, then add them to IgnorePkg until quickshell is rebuilt. The shell works again after a restart. Upstream build fix: quickshell-mirror/quickshell#1235. Same kind of mismatch as #8438.
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.