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-4244GitHub issuePublicReceived

omarchy-launch-browser fails with AppImage browsers managed by Gear Lever

Reported by rosuz · filed Mar 23, 2026Closed upstream on 2026-03-23 by its own reporter rosuz, as a duplicate of #2037 (R-3073). GitHub close reason: duplicate.

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 fails with AppImage browsers managed by Gear Leverrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Omarchy

What's wrong?

omarchy-launch-browser script uses sed to extract the browser executable from .desktop files:
browser_exec=$(sed -n 's/^Exec=\([^ ]\)./\1/p' ...)
Gear Lever (tool for managing AppImages) generates .desktop files with this format:
Exec=env DESKTOPINTEGRATION=1 /path/to/thorium.appimage --no-default-browser-check %U
The sed pattern captures env instead of the actual executable path.
Affected browsers:
- Thorium Browser (AppImage) managed by Gear Lever
- Likely all AppImage browsers managed with Gear Lever and add to them some environment variable
Proposed fix:
Skip Exec=env lines or find the first line with an absolute path:
browser_exec=$(sed -n '/^Exec=env/d; /^Exec=\/[^ ]/ { s/^Exec=\([^ ]\).*/\1/p; q }' ...)

Works for me.

View raw text
### System details

Omarchy

### What's wrong?

omarchy-launch-browser script uses sed to extract the browser executable from .desktop files:
browser_exec=$(sed -n 's/^Exec=\([^ ]*\).*/\1/p' ...)
Gear Lever (tool for managing AppImages) generates .desktop files with this format:
Exec=env DESKTOPINTEGRATION=1 /path/to/thorium.appimage --no-default-browser-check %U
The sed pattern captures env instead of the actual executable path.
Affected browsers:
- Thorium Browser (AppImage) managed by Gear Lever
- Likely all AppImage browsers managed with Gear Lever and add to them some environment variable  
Proposed fix:
Skip Exec=env lines or find the first line with an absolute path:
browser_exec=$(sed -n '/^Exec=env/d; /^Exec=\/[^ ]*/ { s/^Exec=\([^ ]*\).*/\1/p; q }' ...)

Works for me.

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.