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.
Chromium wallet signing windows (Rabby, Phantom) never map under Wayland after 4.0.0
Reported by marioxabel · filed Aug 17, 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
Chromium extension notification windows (Rabby and Phantom Wallet signing prompts) never become an xdg toplevel under Wayland after upgrading to Omarchy 4.0.0 (Quattro). Launching with --ozone-platform=x11 works around it.
Environment
- Omarchy: 4.0.0-1 (
omarchy channel current=4.0.0.alpha), upgraded from 3.8.x on 2026-08-14 - Hyprland: v0.56.2 (
efb50993780079460b0cbed1363e2166a2de1d9f), upgraded 0.56.0-2 → 0.56.2-1 on 2026-08-14 - Chromium: 151.0.7922.137 Arch Linux, upgraded 150.0.7871.128-1 → 151.0.7922.137-1 on 2026-08-14 (same pacman transaction as Hyprland, before
omarchy4.0.0-1 was installed later that morning) - GPU / driver: hybrid Intel UHD Graphics (Comet Lake, i915 / Mesa 26.1.7) + NVIDIA GeForce RTX 2060 Mobile (TU106M, nvidia-open-dkms 610.57.04)
- Machine: Razer Blade 15 Base (Early 2020)
- Channel: 4.0.0.alpha
- Default flags (unchanged ozone lines across the Quattro migration):
--ozone-platform=wayland
--ozone-platform-hint=wayland
- Extensions confirmed: Rabby acmacodkjbdgmoleebolmdjonilkdbch, Phantom bfnaelmomeimhlpmgjnjophhpkkoljpa (both Default and Profile 1)
Steps to reproduce
- Launch Chromium with the stock Omarchy flags (native Wayland)
- Trigger a transaction requiring a signature in Rabby or Phantom
- Extension badge shows the pending request; the signing window never appears
Expected vs actual
Expected: signing window opens and stays until dismissed.
Actual: window does not appear at all, for both wallets. No openwindow event on Hyprland's socket2 (control test: a normal terminal window does emit one), so the popup never becomes an xdg toplevel. Hyprland's tile = true rule for chromium-based-browser therefore cannot be what closed it — nothing was mapped.
Workaround
--ozone-platform=x11 — signing works normally for both wallets.
Additional testing
- Clean profile (
--user-data-dir): not run --disable-gpuunder Wayland: not run- Other extension popups (Bitwarden): not run (see also #6075, which is a size-rule bug on a window that does map)
- Firefox equivalent: not run
Related
Not a duplicate of #6075 (Bitwarden popup maps, wrong size) or #5097 (Edge crash on hover with the tile rule).
Filed by Grok 4.6 via Grok Build.
View raw text
### Summary Chromium extension notification windows (Rabby and Phantom Wallet signing prompts) never become an xdg toplevel under Wayland after upgrading to Omarchy 4.0.0 (Quattro). Launching with `--ozone-platform=x11` works around it. ### Environment - Omarchy: 4.0.0-1 (`omarchy channel current` = `4.0.0.alpha`), upgraded from 3.8.x on 2026-08-14 - Hyprland: v0.56.2 (`efb50993780079460b0cbed1363e2166a2de1d9f`), upgraded 0.56.0-2 → 0.56.2-1 on 2026-08-14 - Chromium: 151.0.7922.137 Arch Linux, upgraded 150.0.7871.128-1 → 151.0.7922.137-1 on 2026-08-14 (same pacman transaction as Hyprland, before `omarchy` 4.0.0-1 was installed later that morning) - GPU / driver: hybrid Intel UHD Graphics (Comet Lake, i915 / Mesa 26.1.7) + NVIDIA GeForce RTX 2060 Mobile (TU106M, nvidia-open-dkms 610.57.04) - Machine: Razer Blade 15 Base (Early 2020) - Channel: 4.0.0.alpha - Default flags (unchanged ozone lines across the Quattro migration): `--ozone-platform=wayland` `--ozone-platform-hint=wayland` - Extensions confirmed: Rabby `acmacodkjbdgmoleebolmdjonilkdbch`, Phantom `bfnaelmomeimhlpmgjnjophhpkkoljpa` (both Default and Profile 1) ### Steps to reproduce 1. Launch Chromium with the stock Omarchy flags (native Wayland) 2. Trigger a transaction requiring a signature in Rabby **or** Phantom 3. Extension badge shows the pending request; the signing window never appears ### Expected vs actual Expected: signing window opens and stays until dismissed. Actual: window does not appear at all, for both wallets. No `openwindow` event on Hyprland's socket2 (control test: a normal terminal window does emit one), so the popup never becomes an xdg toplevel. Hyprland's `tile = true` rule for `chromium-based-browser` therefore cannot be what closed it — nothing was mapped. ### Workaround `--ozone-platform=x11` — signing works normally for both wallets. ### Additional testing - Clean profile (`--user-data-dir`): not run - `--disable-gpu` under Wayland: not run - Other extension popups (Bitwarden): not run (see also #6075, which is a size-rule bug on a window that *does* map) - Firefox equivalent: not run ### Related Not a duplicate of #6075 (Bitwarden popup maps, wrong size) or #5097 (Edge crash on hover with the tile rule). Filed by Grok 4.6 via Grok Build.
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 04:35 UTC