Proof Portal

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

Bash functions broken over SSH: $OMARCHY_PATH not set outside desktop session

Reported by shawnyeager · filed Feb 27, 2026Closed upstream on 2026-02-27 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

Bash functions broken over SSH: $OMARCHY_PATH not set outside desktop sessionrevision 1 · captured 2026-10-04 11:49 UTC via poll

Summary

After today's update, default/bash/functions fails when logging in via SSH with:

-bash: /default/bash/fns/*: No such file or directory

Cause

Commit f6c7b96e ("Use const path") changed default/bash/functions from:

for f in ~/.local/share/omarchy/default/bash/fns/*; do source "$f"; done

to:

for f in $OMARCHY_PATH/default/bash/fns/*; do source "$f"; done

$OMARCHY_PATH is only exported in uwsm/env, which is sourced by the Hyprland desktop session. SSH sessions never load this, so $OMARCHY_PATH is empty and the glob expands to /default/bash/fns/*.

Suggested fix

Either revert to the hardcoded path, or set a default fallback in default/bash/functions:

for f in ${OMARCHY_PATH:-$HOME/.local/share/omarchy}/default/bash/fns/*; do source "$f"; done

Alternatively, default/bash/shell (sourced before functions) could export the default:

export OMARCHY_PATH="${OMARCHY_PATH:-$HOME/.local/share/omarchy}"
View raw text
## Summary

After today's update, `default/bash/functions` fails when logging in via SSH with:

```
-bash: /default/bash/fns/*: No such file or directory
```

## Cause

Commit f6c7b96e ("Use const path") changed `default/bash/functions` from:

```bash
for f in ~/.local/share/omarchy/default/bash/fns/*; do source "$f"; done
```

to:

```bash
for f in $OMARCHY_PATH/default/bash/fns/*; do source "$f"; done
```

`$OMARCHY_PATH` is only exported in `uwsm/env`, which is sourced by the Hyprland desktop session. SSH sessions never load this, so `$OMARCHY_PATH` is empty and the glob expands to `/default/bash/fns/*`.

## Suggested fix

Either revert to the hardcoded path, or set a default fallback in `default/bash/functions`:

```bash
for f in ${OMARCHY_PATH:-$HOME/.local/share/omarchy}/default/bash/fns/*; do source "$f"; done
```

Alternatively, `default/bash/shell` (sourced before `functions`) could export the default:

```bash
export OMARCHY_PATH="${OMARCHY_PATH:-$HOME/.local/share/omarchy}"
```

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.