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.
login startup error: uwsm-app fails with Command not found: "omarchy-hyprland-monitor-watch" although command exists
Reported by SmartALB · filed Apr 30, 2026Closed upstream on 2026-04-30. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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 version: 3.6.0 - Kernel: 6.19.13-arch1-1 - Session: Hyprland (UWSM-managed) - Hyprland: 0.54.3 (hyprland 0.54.3-2 package) - uwsm: 0.26.4-1 - systemd: 260.1-2 - dbus-broker: 37-3 - dbus-broker-units: 37-3
What's wrong?
What's wrong?
Since recent updates, I get a brief startup error notification at login.
The relevant user-journal lines are:
- uwsm_app-daemon: received: app -- omarchy-hyprland-monitor-watch
- uwsm_app-daemon: sent: error 'Error: Command not found: "omarchy-hyprland-monitor-watch"' 1
So uwsm-app fails to launch omarchy-hyprland-monitor-watch during session startup.
Why this seems incorrect
The command is present and executable on disk:
- which omarchy-hyprland-monitor-watch
- /home/alb/.local/share/omarchy/bin/omarchy-hyprland-monitor-watch
- file mode:
- -rwxr-xr-x /home/alb/.local/share/omarchy/bin/omarchy-hyprland-monitor-watch
This indicates the failure is likely due to startup environment/PATH timing in UWSM app launch, not a missing binary.
Reproduction
- Start/update system and log into Omarchy Hyprland session
- Observe brief startup error notification
- Confirm with:
journalctl --user -b 0 --no-pager | rg -i "omarchy-hyprland-monitor-watch|uwsm_app-daemon"
Expected behavior
omarchy-hyprland-monitor-watch is launched successfully at login without any error notification.
Actual behavior
uwsm-app reports:Error: Command not found: "omarchy-hyprland-monitor-watch"
and a startup error notification is shown.
Additional diagnostics (available on request)
omarchy-debug --no-sudo --print- full
journalctl --user -b 0 --no-pagerexcerpt around session start
View raw text
### System details - Omarchy version: 3.6.0 - Kernel: 6.19.13-arch1-1 - Session: Hyprland (UWSM-managed) - Hyprland: 0.54.3 (hyprland 0.54.3-2 package) - uwsm: 0.26.4-1 - systemd: 260.1-2 - dbus-broker: 37-3 - dbus-broker-units: 37-3 ### What's wrong? ## What's wrong? Since recent updates, I get a brief startup error notification at login. The relevant user-journal lines are: - `uwsm_app-daemon: received: app -- omarchy-hyprland-monitor-watch` - `uwsm_app-daemon: sent: error 'Error: Command not found: "omarchy-hyprland-monitor-watch"' 1` So `uwsm-app` fails to launch `omarchy-hyprland-monitor-watch` during session startup. ## Why this seems incorrect The command is present and executable on disk: - `which omarchy-hyprland-monitor-watch` - `/home/alb/.local/share/omarchy/bin/omarchy-hyprland-monitor-watch` - file mode: - `-rwxr-xr-x /home/alb/.local/share/omarchy/bin/omarchy-hyprland-monitor-watch` This indicates the failure is likely due to startup environment/PATH timing in UWSM app launch, not a missing binary. ## Reproduction 1. Start/update system and log into Omarchy Hyprland session 2. Observe brief startup error notification 3. Confirm with: - `journalctl --user -b 0 --no-pager | rg -i "omarchy-hyprland-monitor-watch|uwsm_app-daemon"` ## Expected behavior `omarchy-hyprland-monitor-watch` is launched successfully at login without any error notification. ## Actual behavior `uwsm-app` reports: `Error: Command not found: "omarchy-hyprland-monitor-watch"` and a startup error notification is shown. ## Additional diagnostics (available on request) - `omarchy-debug --no-sudo --print` - full `journalctl --user -b 0 --no-pager` excerpt around session start
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.