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

Starting process with script (waybar or keycombo) brakes current directory script

Reported by phush0 · filed Sep 6, 2025Closed upstream on 2025-09-07 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

Starting process with script (waybar or keycombo) brakes current directory scriptrevision 1 · captured 2026-10-04 11:35 UTC via poll

System details

HP Zbook Ultra G1A, 395+ 64 GB, Atch

What's wrong?

When starting command with script like clicking on CPU icon in waybar ot starting BTOP with supet+T will lead to execute command with alacritty -e, which is alacrity->btop and no shell between, this will lead to cwd with esacalated permitions and omarchy-cmd-terminal-cwd will fail with empty string, so pressing super+return over such window will not open terminal at all. Fix is using:

  if cwd=$(readlink -f "/proc/$shell_pid/cwd" 2>/dev/null); then
    echo "$cwd"
  else
    echo "$HOME"
  fi

to ensure correct handling of this situation.

View raw text
### System details

HP Zbook Ultra G1A, 395+ 64 GB, Atch 

### What's wrong?

When starting command with script like clicking on CPU icon in waybar ot starting BTOP with supet+T will lead to execute command with alacritty -e, which is alacrity->btop and no shell between, this will lead to cwd with esacalated permitions and omarchy-cmd-terminal-cwd will fail with empty string, so pressing super+return over such window will not open terminal at all. Fix is using:

```
  if cwd=$(readlink -f "/proc/$shell_pid/cwd" 2>/dev/null); then
    echo "$cwd"
  else
    echo "$HOME"
  fi
```

to ensure correct handling of this situation.

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.