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 crashes (SIGTRAP/int3) during OAuth popup launch on Hyprland, works on KDE Plasma
Reported by wisangdg · filed Aug 26, 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
Description
Chromium crashes with SIGTRAP (self-inflicted int3) during startup when launched as a new process for OAuth flows (e.g., HoYoverse Google login). The crash happens during ChromeMain initialization, before any content loads, causing a crash loop (~20 crashes).
Works fine on KDE Plasma (Wayland). Only crashes on Hyprland (Omarchy default).
Steps to reproduce
- Install Chromium with
--oauth2-client-id/--oauth2-client-secretin~/.config/chromium-flags.conf(viaomarchy-install-chromium-google-account) - Open a site with Google OAuth login (e.g., HoYoverse)
- Click "Login with Google" — this launches a new Chromium process with the OAuth URL
- New Chromium process crashes immediately with
int3
Evidence
- Signal:
SIGTRAP (int3),si_code: SI_KERNEL— kernel log confirmstrap int3executed by the process itself - Stack: Only
_start → __libc_start_main → ChromeMain → int3— single thread, very early initialization - Deterministic: Same instruction offset (
chromium + 0x10c634f1) every crash - Not OOM: 8.2 GiB available
- Normal browsing works fine — only new OAuth popup processes crash
What works
| Flag | OAuth crash? |
|---|---|
| (default) | Crashes |
--ozone-platform=x11 | Works |
--disable-gpu | Works |
--no-extensions | Works |
Environment
- Omarchy: 4.0.1-1
- Chromium: 151.0.7922.173-1
- Hyprland: 0.56.2
- GPU: NVIDIA (hybrid mode via supergfxd,
nvidia-drmdriver) - Compositor: Hyprland (Wayland)
- Portal: xdg-desktop-portal-hyprland
Suspected cause
Chromium's Ozone/Wayland GPU compositing initialization fails during ChromeMain startup when a new process is launched. The --disable-gpu workaround confirms it's GPU-related. The fact that KDE Plasma (KWin compositor) works fine suggests a difference in how Hyprland handles Wayland protocol or GPU initialization for new windows.
Workaround
Add --disable-gpu to ~/.config/chromium-flags.conf.
View raw text
### Description Chromium crashes with `SIGTRAP` (self-inflicted `int3`) during startup when launched as a new process for OAuth flows (e.g., HoYoverse Google login). The crash happens during `ChromeMain` initialization, before any content loads, causing a crash loop (~20 crashes). **Works fine on KDE Plasma (Wayland).** Only crashes on Hyprland (Omarchy default). ### Steps to reproduce 1. Install Chromium with `--oauth2-client-id` / `--oauth2-client-secret` in `~/.config/chromium-flags.conf` (via `omarchy-install-chromium-google-account`) 2. Open a site with Google OAuth login (e.g., HoYoverse) 3. Click "Login with Google" — this launches a new Chromium process with the OAuth URL 4. New Chromium process crashes immediately with `int3` ### Evidence - **Signal:** `SIGTRAP (int3)`, `si_code: SI_KERNEL` — kernel log confirms `trap int3` executed by the process itself - **Stack:** Only `_start → __libc_start_main → ChromeMain → int3` — single thread, very early initialization - **Deterministic:** Same instruction offset (`chromium + 0x10c634f1`) every crash - **Not OOM:** 8.2 GiB available - **Normal browsing works fine** — only new OAuth popup processes crash ### What works | Flag | OAuth crash? | |------|-------------| | (default) | **Crashes** | | `--ozone-platform=x11` | Works | | `--disable-gpu` | Works | | `--no-extensions` | Works | ### Environment - **Omarchy:** 4.0.1-1 - **Chromium:** 151.0.7922.173-1 - **Hyprland:** 0.56.2 - **GPU:** NVIDIA (hybrid mode via supergfxd, `nvidia-drm` driver) - **Compositor:** Hyprland (Wayland) - **Portal:** xdg-desktop-portal-hyprland ### Suspected cause Chromium's Ozone/Wayland GPU compositing initialization fails during `ChromeMain` startup when a new process is launched. The `--disable-gpu` workaround confirms it's GPU-related. The fact that KDE Plasma (KWin compositor) works fine suggests a difference in how Hyprland handles Wayland protocol or GPU initialization for new windows. ### Workaround Add `--disable-gpu` to `~/.config/chromium-flags.conf`.
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
- Related PRpr/11907· confirmed
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 09:16 UTC