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.
Bar foreground stuck at ~70% opacity on one monitor after toggling transparency off (multi-monitor)
Reported by uMaj35ty · filed Aug 24, 2026 · open at source
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
System details
AMD Ryzen 7 5800X, NVIDIA RTX 5060 Ti, Omarchy 4.0.0-1 (shell: quickshell-git 0.3.0.r20.g28771c7-2, Hyprland 0.56.2-1). Dual monitors: DP-3 2560x1440 (primary) + HDMI-A-1 1920x1080. Theme: matte-black.
What's wrong?
After toggling the bar's transparency mode on and back off (double-click on empty bar space), the bar on one monitor gets permanently stuck rendering its foreground at ~70% opacity. The bar background stays the normal opaque bar.background (#121212), but every text glyph and icon renders at 70% of bar.text — #bebebe comes out as #8a8a8a. The bar is still readable but visibly faded/washed-out. The other monitor's bar stays correct.
Characteristics of the stuck state:
- Persists indefinitely — across workspace switches, further
omarchy bar transparent togglecalls, and edits toshell.json(bar.transparentis correctlyfalseat this point). - In transparent mode the same bar renders the computed text color correctly; toggling back off returns it to the dimmed state.
- Attached to the specific Bar instance, not to keyboard focus or monitor identity (moving focus to the other monitor does not move the dimming).
- Cleared by
omarchy restart shell.
Steps to reproduce
- Use a dual-monitor setup (bar on both monitors).
- Double-click an empty spot on one monitor's bar (or run
omarchy bar transparent toggle) to enable transparent mode. - Toggle it off again.
- The bar where the toggle happened renders all text/icons at ~70% opacity; the other monitor's bar is unaffected.
Pixel-level verification (screenshot the top 30 px of each monitor, count exact-color pixels):
| Monitor | Bar background | Foreground color |
|---|---|---|
| DP-3 (toggled, stuck) | #121212 | #8a8a8a (5176 px) — exactly #bebebe at 70% over #121212 |
| HDMI-A-1 (untouched) | #121212 | #bebebe (349 px) — theme bar.text |
After omarchy restart shell, DP-3 returns to 349 exact-#bebebe pixels, identical to the healthy monitor.
Expected
With bar.transparent: false, barForeground should resolve to theme bar.text on every monitor. setRequestedTransparency(false) resets useTransparentForeground/transparent per Bar instance (shell/plugins/bar/Bar.qml), but something in the double-toggle path leaves one instance rendering its foreground at reduced opacity.
Workaround
omarchy restart shell
Diagnostics
omarchy debug --no-sudo --print excerpt:
Omarchy Package: omarchy 4.0.0-1
Kernel 7.1.8-arch1-3 arch x86_64
Desktop Hyprland v0.56.2 vt 1 dm SDDM Distro Omarchy
CPU: AMD Ryzen 7 5800X (8 cores / 16 threads)
GPU: NVIDIA GeForce RTX 5060 Ti (discrete)
Monitor-1 DP-3 model P2710R res 2560x1440
Monitor-2 HDMI-A-1 model GM116HD res 1920x1080Full log and side-by-side screenshots of the two bars to follow as attachments.
View raw text
### System details AMD Ryzen 7 5800X, NVIDIA RTX 5060 Ti, Omarchy 4.0.0-1 (shell: quickshell-git 0.3.0.r20.g28771c7-2, Hyprland 0.56.2-1). Dual monitors: DP-3 2560x1440 (primary) + HDMI-A-1 1920x1080. Theme: matte-black. ### What's wrong? After toggling the bar's transparency mode **on and back off** (double-click on empty bar space), the bar on one monitor gets permanently stuck rendering its foreground at ~70% opacity. The bar background stays the normal opaque `bar.background` (`#121212`), but every text glyph and icon renders at 70% of `bar.text` — `#bebebe` comes out as `#8a8a8a`. The bar is still readable but visibly faded/washed-out. The other monitor's bar stays correct. Characteristics of the stuck state: - Persists indefinitely — across workspace switches, further `omarchy bar transparent toggle` calls, and edits to `shell.json` (`bar.transparent` is correctly `false` at this point). - In transparent mode the same bar renders the computed text color correctly; toggling back off returns it to the dimmed state. - Attached to the specific Bar instance, not to keyboard focus or monitor identity (moving focus to the other monitor does not move the dimming). - Cleared by `omarchy restart shell`. ### Steps to reproduce 1. Use a dual-monitor setup (bar on both monitors). 2. Double-click an empty spot on one monitor's bar (or run `omarchy bar transparent toggle`) to enable transparent mode. 3. Toggle it off again. 4. The bar where the toggle happened renders all text/icons at ~70% opacity; the other monitor's bar is unaffected. Pixel-level verification (screenshot the top 30 px of each monitor, count exact-color pixels): | Monitor | Bar background | Foreground color | |---|---|---| | DP-3 (toggled, stuck) | `#121212` | `#8a8a8a` (5176 px) — exactly `#bebebe` at 70% over `#121212` | | HDMI-A-1 (untouched) | `#121212` | `#bebebe` (349 px) — theme `bar.text` | After `omarchy restart shell`, DP-3 returns to 349 exact-`#bebebe` pixels, identical to the healthy monitor. ### Expected With `bar.transparent: false`, `barForeground` should resolve to theme `bar.text` on every monitor. `setRequestedTransparency(false)` resets `useTransparentForeground`/`transparent` per Bar instance (shell/plugins/bar/Bar.qml), but something in the double-toggle path leaves one instance rendering its foreground at reduced opacity. ### Workaround `omarchy restart shell` ### Diagnostics `omarchy debug --no-sudo --print` excerpt: ``` Omarchy Package: omarchy 4.0.0-1 Kernel 7.1.8-arch1-3 arch x86_64 Desktop Hyprland v0.56.2 vt 1 dm SDDM Distro Omarchy CPU: AMD Ryzen 7 5800X (8 cores / 16 threads) GPU: NVIDIA GeForce RTX 5060 Ti (discrete) Monitor-1 DP-3 model P2710R res 2560x1440 Monitor-2 HDMI-A-1 model GM116HD res 1920x1080 ``` Full log and side-by-side screenshots of the two bars to follow as attachments.
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 08:36 UTC