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.
Hyprland 0.54 syntax change and grouped windows interaction changes
Reported by edwardkimy · filed Feb 28, 2026Closed upstream on 2026-02-28 by commit bce826367585 (closed by dhh). GitHub close reason: completed.
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
Omarchy 3.4.0, Hyprland 0.54.0
What's wrong?
Using edge branch. After updating to hyprland 0.54 I started having a couple of issues.
- Hyprland introduced syntax changes for specific functions. One of them, being windows split toggle:
bindd = SUPER, J, Toggle window split, togglesplit
has been replaced bybindd = SUPER, J, Toggle window split, layoutmsg, togglesplit
- There are issues with interaction between grouped, full-screen and floating windows.
2.1. When I have a windows group open, starting floating windows runs them inside of that group (non floating).
2.2. Screensaver switch a windows group into full-screen mode when triggered.
I came up with this workaround, using "group barred" window rules:
2.1. Using this window rule:windowrule = float on, group barred, size 1200 800, match:class ^(org\.gnome\.(Calendar|Weather)|vesktop)$
2.2. And this window rule for Steam and screensaver:windowrule = group barred, match:class ^(steam|org.omarchy.screensaver)$
At this point it is unknown if floating window interaction is intentional, but syntax change for "layoutmsg" format is permanent and would require binding rewrite.
View raw text
### System details Omarchy 3.4.0, Hyprland 0.54.0 ### What's wrong? Using edge branch. After updating to hyprland 0.54 I started having a couple of issues. 1. Hyprland introduced syntax changes for specific functions. One of them, being windows split toggle: `bindd = SUPER, J, Toggle window split, togglesplit` has been replaced by `bindd = SUPER, J, Toggle window split, layoutmsg, togglesplit` 2. There are issues with interaction between grouped, full-screen and floating windows. 2.1. When I have a windows group open, starting floating windows runs them inside of that group (non floating). 2.2. Screensaver switch a windows group into full-screen mode when triggered. I came up with this workaround, using "group barred" window rules: 2.1. Using this window rule: `windowrule = float on, group barred, size 1200 800, match:class ^(org\.gnome\.(Calendar|Weather)|vesktop)$` 2.2. And this window rule for Steam and screensaver: `windowrule = group barred, match:class ^(steam|org.omarchy.screensaver)$` At this point it is unknown if floating window interaction is intentional, but syntax change for "layoutmsg" format is permanent and would require binding rewrite.
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.