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.
Browsers' native "Set as default" button fails under the Omarchy session
Reported by felixzsh · filed Aug 6, 2026Closed upstream on 2026-08-07 by the merge of PR #6616 (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 quattro
What's wrong?
❯ xdg-settings set default-web-browser vivaldi-stable.desktop
xdg-settings: $BROWSER is set and can't be changed with xdg-settings
Browsers' own "Set as default" buttons go through xdg-settings, so they fail for every browser — Vivaldi, Firefox, Zen, and the Chromium family alike. In practice, pressing "Set as default" in Vivaldi silently fails: the default stays on Chromium, so omarchy-launch-browser and web apps keep opening Chromium.
#6356 added env -u BROWSER to Omarchy's own browser commands, which makes omarchy default browser <x> work — but it does not fully resolve this case: $BROWSER is still exported in the session, so the browsers' own buttons still cannot change the default.
View raw text
### System details omarchy quattro ### What's wrong? ❯ xdg-settings set default-web-browser vivaldi-stable.desktop xdg-settings: $BROWSER is set and can't be changed with xdg-settings Browsers' own "Set as default" buttons go through xdg-settings, so they fail for every browser — Vivaldi, Firefox, Zen, and the Chromium family alike. In practice, pressing "Set as default" in Vivaldi silently fails: the default stays on Chromium, so omarchy-launch-browser and web apps keep opening Chromium. #6356 added env -u BROWSER to Omarchy's own browser commands, which makes omarchy default browser <x> work — but it does not fully resolve this case: $BROWSER is still exported in the session, so the browsers' own buttons still cannot change the default.
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.