Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4516GitHub issuePublicReceived

omarchy-launch-browser launches an empty executable after unsetting BROWSER

Reported by alaeddin14 · filed Jul 28, 2026Closed upstream on 2026-07-29 by the merge of PR #6424 (closed by dhh). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

omarchy-launch-browser launches an empty executable after unsetting BROWSERrevision 1 · captured 2026-10-04 11:56 UTC via poll

System details

Omarchy 4.0.0.r1429.gf4e8470-1

What's wrong?

After updating to Omarchy 4.0.0.r1429.gf4e8470-1, applications that use the $BROWSER environment variable can no longer open URLs. I encountered this during a Google OAuth flow: the local authorization server started, but Chromium never opened, and the flow eventually timed out.

The default browser is configured correctly:

xdg-mime query default x-scheme-handler/http
xdg-mime query default x-scheme-handler/https
xdg-mime query default text/html

All three commands return:

chromium.desktop

The session has the Omarchy browser wrapper configured:

echo "$BROWSER"
omarchy-launch-browser

However, the lookup used by omarchy-launch-browser returns an empty value:

env -u BROWSER xdg-settings get default-web-browser

The command exits successfully but produces no output. As a result, browser_exec is empty in /usr/share/omarchy/bin/omarchy-launch-browser, and the wrapper schedules a command equivalent to:

uwsm-app -- "" "<URL>"

The user journal confirms the failure:

uwsm_app-daemon: sent: error 'Error: Command not found: ""' 1
omarchy-browser-*.service: Main process exited, code=exited, status=1/FAILURE

Expected Behavior

omarchy-launch-browser <URL> should resolve chromium.desktop to /usr/bin/chromium and open the supplied URL.

Suspected Regression

This appears related to commit `e61ff1e`, which changed the lookup in omarchy-launch-browser from:

xdg-settings get default-web-browser

to:

env -u BROWSER xdg-settings get default-web-browser

The MIME associations are valid, but the latter command returns an empty result in this Hyprland/Omarchy session.

View raw text
### System details

Omarchy 4.0.0.r1429.gf4e8470-1

### What's wrong?

After updating to Omarchy `4.0.0.r1429.gf4e8470-1`, applications that use the `$BROWSER` environment variable can no longer open URLs. I encountered this during a Google OAuth flow: the local authorization server started, but Chromium never opened, and the flow eventually timed out.

The default browser is configured correctly:

```bash
xdg-mime query default x-scheme-handler/http
xdg-mime query default x-scheme-handler/https
xdg-mime query default text/html
```

All three commands return:

```text
chromium.desktop
```

The session has the Omarchy browser wrapper configured:

```bash
echo "$BROWSER"
```

```text
omarchy-launch-browser
```

However, the lookup used by `omarchy-launch-browser` returns an empty value:

```bash
env -u BROWSER xdg-settings get default-web-browser
```

The command exits successfully but produces no output. As a result, `browser_exec` is empty in `/usr/share/omarchy/bin/omarchy-launch-browser`, and the wrapper schedules a command equivalent to:

```text
uwsm-app -- "" "<URL>"
```

The user journal confirms the failure:

```text
uwsm_app-daemon: sent: error 'Error: Command not found: ""' 1
omarchy-browser-*.service: Main process exited, code=exited, status=1/FAILURE
```


### Expected Behavior

`omarchy-launch-browser <URL>` should resolve `chromium.desktop` to `/usr/bin/chromium` and open the supplied URL.

### Suspected Regression

This appears related to commit [`e61ff1e`](https://github.com/basecamp/omarchy/commit/e61ff1ef4fa5170218b50237f4c12f601d728841), which changed the lookup in `omarchy-launch-browser` from:

```bash
xdg-settings get default-web-browser
```

to:

```bash
env -u BROWSER xdg-settings get default-web-browser
```

The MIME associations are valid, but the latter command returns an empty result in this Hyprland/Omarchy session.

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.