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.
Microsoft Edge crashes under Wayland with tile rule on hover
Reported by mihapus · filed Mar 22, 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
Summary
Microsoft Edge segfaults when hovering over images on certain sites (e.g. omarchythemes.com theme detail pages). The crash is caused by the interaction between Edge's native Wayland popup/overlay handling and the tile on window rule in browser.conf.
Details
Edge is recognized in omarchy's window rules and launch scripts, but unlike Brave and Chromium, it has no flags config file shipped in ~/.local/share/omarchy/config/. The correct filename for Edge is microsoft-edge-stable-flags.conf (not microsoft-edge-flags.conf).
Even with a flags file matching the other browsers' Wayland flags, Edge 146 crashes (SIGSEGV) when:
- Running under native Wayland (--ozone-platform=wayland)
- The tile on rule from browser.conf is active
- The user hovers over certain page elements (images on theme detail pages)
The GPU process also logs: '--ozone-platform=wayland' is not compatible with Vulkan
What was tested
| Approach | Result |
|---|---|
--disable-gpu | Still crashes on hover |
--disable-gpu-compositing | Still crashes |
--disable-vulkan | Still crashes |
--disable-extensions | Still crashes |
--use-gl=angle --use-angle=gl | Still crashes |
tile off window rule | No crash, but window spazzes on hover |
--ozone-platform=x11 (XWayland) | Works perfectly |
Environment
- Edge 146.0.3856.72
- Hyprland 0.54.2
- Intel Iris Xe Graphics (Raptor Lake-P)
- Monitor: 1920x1200 @ scale 1.5
Workaround
Create ~/.config/microsoft-edge-stable-flags.conf:
--ozone-platform=x11
--force-device-scale-factor=1.5
--enable-features=TouchpadOverscrollHistoryNavigation
--load-extension=~/.local/share/omarchy/default/chromium/extensions/copy-urlNote: --force-device-scale-factor must match the monitor scale from hyprctl monitors.
Suggestion
Ship a microsoft-edge-stable-flags.conf in ~/.local/share/omarchy/config/ using --ozone-platform=x11 (since native Wayland is unstable in Edge), along with a scale factor that matches the user's display. Alternatively, the tile on rule in browser.conf could be scoped more narrowly to avoid triggering the Edge crash.
View raw text
## Summary Microsoft Edge segfaults when hovering over images on certain sites (e.g. omarchythemes.com theme detail pages). The crash is caused by the interaction between Edge's native Wayland popup/overlay handling and the `tile on` window rule in `browser.conf`. ## Details Edge is recognized in omarchy's window rules and launch scripts, but unlike Brave and Chromium, it has no flags config file shipped in `~/.local/share/omarchy/config/`. The correct filename for Edge is `microsoft-edge-stable-flags.conf` (not `microsoft-edge-flags.conf`). Even with a flags file matching the other browsers' Wayland flags, Edge 146 crashes (SIGSEGV) when: - Running under native Wayland (`--ozone-platform=wayland`) - The `tile on` rule from `browser.conf` is active - The user hovers over certain page elements (images on theme detail pages) The GPU process also logs: `'--ozone-platform=wayland' is not compatible with Vulkan` ### What was tested | Approach | Result | |----------|--------| | `--disable-gpu` | Still crashes on hover | | `--disable-gpu-compositing` | Still crashes | | `--disable-vulkan` | Still crashes | | `--disable-extensions` | Still crashes | | `--use-gl=angle --use-angle=gl` | Still crashes | | `tile off` window rule | No crash, but window spazzes on hover | | `--ozone-platform=x11` (XWayland) | Works perfectly | ### Environment - Edge 146.0.3856.72 - Hyprland 0.54.2 - Intel Iris Xe Graphics (Raptor Lake-P) - Monitor: 1920x1200 @ scale 1.5 ## Workaround Create `~/.config/microsoft-edge-stable-flags.conf`: ``` --ozone-platform=x11 --force-device-scale-factor=1.5 --enable-features=TouchpadOverscrollHistoryNavigation --load-extension=~/.local/share/omarchy/default/chromium/extensions/copy-url ``` Note: `--force-device-scale-factor` must match the monitor scale from `hyprctl monitors`. ## Suggestion Ship a `microsoft-edge-stable-flags.conf` in `~/.local/share/omarchy/config/` using `--ozone-platform=x11` (since native Wayland is unstable in Edge), along with a scale factor that matches the user's display. Alternatively, the `tile on` rule in `browser.conf` could be scoped more narrowly to avoid triggering the Edge crash.
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 02:43 UTC