You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bar foreground stuck at ~70% opacity on one monitor after toggling transparency off (multi-monitor) #8024
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
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 1920x1080
Full log and side-by-side screenshots of the two bars to follow as attachments.
Reviewed against quattro at c352b62 by reading the source. Nothing was run: this needs your session's state, which a worker cannot recreate.
The measurements point at something other than the text colour. Nothing in the transparency code (setRequestedTransparency, the barForeground animation, the text-colour sampler) can leave the foreground at 70% of bar.text, and the bar's colour state is shared by every monitor rather than held per monitor. What fits everything you describe is the full-screen omarchy-bar-move-ghost overlay staying open after a bar-move gesture. That is the edge preview shown while you drag the bar to another side of the screen (shell/plugins/bar/Bar.qml:1479-1530). It appears only on the monitor where the gesture started. Outside transparent mode, its slab over the bar's edge is drawn at 0.7 opacity, filled with the bar background and outlined with a 1px line in the bar text colour. That outline comes out at exactly #8a8a8a over #121212. A 1px outline around a 2560-wide bar is about 5,170 pixels, which matches your 5,176. The fill leaves the background at #121212 but darkens the glyphs underneath. In transparent mode the fill is transparent, so the bar looks right again. Nothing clears the overlay except the gesture's own release, which is why only a shell restart cleared it. Double-clicking the bar can start a move once the pointer drifts a few pixels between the press and the release.
If this is it, it is the same bug as #7276, which #7563 addresses. I haven't closed this as a duplicate yet, because your screenshots haven't been checked for where those pixels sit. Next time the bar fades, two checks would settle it:
hyprctl layers | grep bar-move-ghost: a line there means the overlay is stuck.
Press and hold on an empty part of the bar's centre for about half a second on that monitor, then release without moving. If the fade clears, that was the overlay.
The diagnosis was reviewed by Codex at medium effort, which agreed that the overlay is the leading explanation. It added that a normal double-click still delivers the release, so something must also interrupt the gesture. It also noted that the 26px default bar height gives 5,168 pixels rather than 5,176, so the match is close rather than exact. This waits on your answer to the checks above.
Activity
uMaj35ty commentedon Aug 24, 2026
uMaj35ty commentedon Aug 24, 2026
omarchy-debug.log
omarchybot commentedon Oct 9, 2026
Reviewed against
quattroat c352b62 by reading the source. Nothing was run: this needs your session's state, which a worker cannot recreate.The measurements point at something other than the text colour. Nothing in the transparency code (
setRequestedTransparency, thebarForegroundanimation, the text-colour sampler) can leave the foreground at 70% ofbar.text, and the bar's colour state is shared by every monitor rather than held per monitor. What fits everything you describe is the full-screenomarchy-bar-move-ghostoverlay staying open after a bar-move gesture. That is the edge preview shown while you drag the bar to another side of the screen (shell/plugins/bar/Bar.qml:1479-1530). It appears only on the monitor where the gesture started. Outside transparent mode, its slab over the bar's edge is drawn at 0.7 opacity, filled with the bar background and outlined with a 1px line in the bar text colour. That outline comes out at exactly#8a8a8aover#121212. A 1px outline around a 2560-wide bar is about 5,170 pixels, which matches your 5,176. The fill leaves the background at#121212but darkens the glyphs underneath. In transparent mode the fill is transparent, so the bar looks right again. Nothing clears the overlay except the gesture's own release, which is why only a shell restart cleared it. Double-clicking the bar can start a move once the pointer drifts a few pixels between the press and the release.If this is it, it is the same bug as #7276, which #7563 addresses. I haven't closed this as a duplicate yet, because your screenshots haven't been checked for where those pixels sit. Next time the bar fades, two checks would settle it:
hyprctl layers | grep bar-move-ghost: a line there means the overlay is stuck.The diagnosis was reviewed by Codex at medium effort, which agreed that the overlay is the leading explanation. It added that a normal double-click still delivers the release, so something must also interrupt the gesture. It also noted that the 26px default bar height gives 5,168 pixels rather than 5,176, so the match is close rather than exact. This waits on your answer to the checks above.