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.
Brave (brave-bin) hangs under Omarchy/Hyprland unless env is sanitized
Reported by avaldez-gr · filed Sep 4, 2025Closed upstream on 2025-09-05 by its own reporter avaldez-gr. GitHub close reason: completed. Closed by its own reporter — not by itself 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
After installing Ghostty and tweaking Hyprland bindings (later reverted), Brave (brave-bin) stopped launching on my Omarchy/Hyprland setup. Processes appear in btop, but no window ever shows. Chromium launches fine. If I launch Brave with a sanitized environment, it works immediately.
What Happens
- Launching brave from terminal, menu, or keybind: no window, but processes are running.
- Chromium works normally.
- brave --enable-logging=stderr --v=1 shows the GPU process starts; prior tests showed VA-API init messages.
- strace shows the browser waiting (lots of futex/epoll_wait) rather than crashing.
What I tried
- Reverted bindings; uninstalled Ghostty.
- Nuked Brave profile + flags (~/.config/BraveSoftware, ~/.config/brave-flags.conf).
- Reinstalled brave-bin.
- VA-API is healthy (vainfo OK); Chromium runs fine.
- For testing, created a wrapper that unsets the suspect vars before exec’ing Brave → works.
- Clearing XDG_BACKEND from user env helped, but I still had to sanitize additional vars for brave-bin to reliably launch.
Really getting frustrated and trying to figure out how I can resolve this.
View raw text
After installing Ghostty and tweaking Hyprland bindings (later reverted), Brave (`brave-bin)` stopped launching on my Omarchy/Hyprland setup. Processes appear in btop, but no window ever shows. Chromium launches fine. If I launch Brave with a sanitized environment, it works immediately. ## What Happens - Launching brave from terminal, menu, or keybind: no window, but processes are running. - Chromium works normally. - brave --enable-logging=stderr --v=1 shows the GPU process starts; prior tests showed VA-API init messages. - strace shows the browser waiting (lots of futex/epoll_wait) rather than crashing. ## What I tried - Reverted bindings; uninstalled Ghostty. - Nuked Brave profile + flags (~/.config/BraveSoftware, ~/.config/brave-flags.conf). - Reinstalled brave-bin. - VA-API is healthy (vainfo OK); Chromium runs fine. - For testing, created a wrapper that unsets the suspect vars before exec’ing Brave → works. - Clearing XDG_BACKEND from user env helped, but I still had to sanitize additional vars for brave-bin to reliably launch. Really getting frustrated and trying to figure out how I can resolve this.
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.