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.
Walker and terminal unavailable, 'Error Command not found: "--working-directory"'
Reported by sedubois · filed Oct 19, 2025Closed upstream on 2025-10-23 by its own reporter sedubois. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
Omarchy 3.1
What's wrong?
After upgrading to Omarchy 3.1 (accepting the new keybinding defaults) and rebooting to upgrade the kernel, got these issues:
- Omarchy started on a black screen (no waybar, no wallpaper)
- super-Esc and super-space don't open the walker menu, nothing happens
- super-Enter doesn't start the terminal, shows a notification 'Error Command not found: "--working-directory"'
- launching the btop activity monitor with super-shift-T fails with 'Error Command not found: "-e"'
After restarting again, the waybar and wallpaper did reappear but still cannot open the walker menu by clicking the Omarchy icon in the waybar, still can’t open the terminal.
I can switch to a terminal-only session using Ctrl-Alt-F3 where, if I replace $terminal = uwsm app -- $TERMINAL with $terminal = uwsm app -- /usr/bin/alacritty and switch back to Hyprland using Ctrl-Alt-F1, then I can now open the btop activity monitor using Cmd-shift-T. This seems to indicate that a $TERMINAL environment variable is expected to be defined somewhere but is missing. After this workaround however, I still cannot open a regular terminal with super-Enter or by any other known means.
View raw text
### System details Omarchy 3.1 ### What's wrong? After upgrading to Omarchy 3.1 (accepting the new keybinding defaults) and rebooting to upgrade the kernel, got these issues: - Omarchy started on a black screen (no waybar, no wallpaper) - super-Esc and super-space don't open the walker menu, nothing happens - super-Enter doesn't start the terminal, shows a notification 'Error Command not found: "--working-directory"' - launching the btop activity monitor with super-shift-T fails with 'Error Command not found: "-e"' After restarting again, the waybar and wallpaper did reappear but still cannot open the walker menu by clicking the Omarchy icon in the waybar, still can’t open the terminal. I can switch to a terminal-only session using Ctrl-Alt-F3 where, if I replace `$terminal = uwsm app -- $TERMINAL` with `$terminal = uwsm app -- /usr/bin/alacritty` and switch back to Hyprland using Ctrl-Alt-F1, then I can now open the btop activity monitor using Cmd-shift-T. This seems to indicate that a `$TERMINAL` environment variable is expected to be defined somewhere but is missing. After this workaround however, I still cannot open a regular terminal with super-Enter or by any other known means.
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.