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.
launch webapp fails when default browser is Firefox (no Chromium installed)
Reported by alkevintan · filed Aug 15, 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
What happened
omarchy launch webapp https://messenger.com fails with:
error: path "--app=https://messenger.com" does not exist!Expected: messenger.com opens as a web app (app mode) in the default browser.
Reproduction
- Install Firefox as the only browser and set it as default (
xdg-settings get default-web-browser→firefox.desktop). - Run
omarchy launch webapp https://messenger.com.
Root cause
/usr/share/omarchy/bin/omarchy-launch-webapp whitelists only Chromium-family
browsers and falls back to chromium.desktop for anything else:
case $browser in
google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*) ;;
*) browser="chromium.desktop" ;;
esac
exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}"With Firefox set as default, chromium.desktop doesn't exist, so the sed
extraction returns an empty binary path and the command degrades to:
uwsm-app -- --app="https://messenger.com"uwsm-app then treats --app=... as the executable path → error: path "... does not exist!".
Suggested fix: add Firefox to the supported browser list (Firefox supports--app=<url>), and/or fall back to the actual default browser's desktop file
instead of hardcoding chromium.desktop.
System details
- Omarchy: 4.0.0-1
- Arch x86_64, Intel Celeron N4020 (GeminiLake UHD 600)
- Default browser:
firefox.desktop
View raw text
## What happened
`omarchy launch webapp https://messenger.com` fails with:
```
error: path "--app=https://messenger.com" does not exist!
```
Expected: messenger.com opens as a web app (app mode) in the default browser.
## Reproduction
1. Install Firefox as the only browser and set it as default (`xdg-settings get default-web-browser` → `firefox.desktop`).
2. Run `omarchy launch webapp https://messenger.com`.
## Root cause
`/usr/share/omarchy/bin/omarchy-launch-webapp` whitelists only Chromium-family
browsers and falls back to `chromium.desktop` for anything else:
```bash
case $browser in
google-chrome* | brave* | microsoft-edge* | opera* | vivaldi* | helium*) ;;
*) browser="chromium.desktop" ;;
esac
exec setsid uwsm-app -- $(sed -n 's/^Exec=\([^ ]*\).*/\1/p' {~/.local,~/.nix-profile,/usr}/share/applications/$browser 2>/dev/null | head -1) --app="$1" "${@:2}"
```
With Firefox set as default, `chromium.desktop` doesn't exist, so the `sed`
extraction returns an empty binary path and the command degrades to:
```
uwsm-app -- --app="https://messenger.com"
```
`uwsm-app` then treats `--app=...` as the executable path → `error: path "... does not exist!"`.
Suggested fix: add Firefox to the supported browser list (Firefox supports
`--app=<url>`), and/or fall back to the actual default browser's desktop file
instead of hardcoding `chromium.desktop`.
## System details
- Omarchy: 4.0.0-1
- Arch x86_64, Intel Celeron N4020 (GeminiLake UHD 600)
- Default browser: `firefox.desktop`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/11044· confirmed
- Related PRpr/10446· confirmed
- Related PRpr/11975· 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 04:14 UTC