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.
Potential misconfiguration in Opacity window rules in config files
Reported by linux-fertxo · filed Oct 7, 2025Closed upstream on 2026-02-01 by dhh. 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
What do you need?
Hi there, great job with your config overall! Congrats!
I've noticed that in default/hypr/apps/browser.conf there's a rule that intends to give a subtle opacity ( 1 0.97 ), slightly different to general opacity set in default/hypr/windows.conf ( 0.97 0.9 )
The fact is that opacity in hyprland is multiplicative, so the result is an actual opacity of ( *`10.97 = 0.97 and 0.970.9 = 0.873`* ) for the browser windows, so they're a little more transparent that if we had only one rule. If this is the intended result then forgive me.
But if I understand correctly, the desired result is just the opposite. For this purpose Hyprland uses the "override" keyword. Thus, `opacity 1 override 0.97 override` will set opacity to `1, 0.97` regardless of any previous rules.
I hope this has been helpful. Keep up the great work!
View raw text
### What do you need? Hi there, great job with your config overall! Congrats! I've noticed that in `default/hypr/apps/browser.conf` there's a rule that intends to give a subtle opacity ( `1 0.97` ), slightly different to general opacity set in `default/hypr/windows.conf` ( `0.97 0.9` ) The fact is that opacity in hyprland is multiplicative, so the result is an actual opacity of ( **`1*0.97 = 0.97 and 0.97*0.9 = 0.873`** ) for the browser windows, so they're a little more transparent that if we had only one rule. If this is the intended result then forgive me. But if I understand correctly, the desired result is just the opposite. For this purpose Hyprland uses the "override" keyword. Thus, **`opacity 1 override 0.97 override`** will set opacity to **`1, 0.97`** regardless of any previous rules. I hope this has been helpful. Keep up the great work! [Source](https://wiki.hypr.land/Configuring/Window-Rules/#notes)
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.