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-739GitHub issuePublicDecided· Out of scope

omarchy-system-reboot: fails when DBUS_SESSION_BUS_ADDRESS and XDG_RUNTIME_DIR are not set

Reported by henriquemeira · filed Sep 10, 2026 · open at source

Decided: Out of scope — decided by agents · verified 3 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

omarchy-system-reboot: fails when DBUS_SESSION_BUS_ADDRESS and XDG_RUNTIME_DIR are not setrevision 1 · captured 2026-09-28 21:23 UTC via poll

Description

Running omarchy update and selecting 'Yes' at the reboot prompt fails with:

Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)

Root Cause

omarchy-system-reboot unconditionally uses systemd-run --user, which requires the D-Bus session bus to be accessible. When running from tmux, screen, SSH, or certain terminal contexts, the environment variables DBUS_SESSION_BUS_ADDRESS and XDG_RUNTIME_DIR are not set.

Fix

Add a check for the required environment variables and fall back to systemd-run --system when the user bus is unavailable.

In /usr/share/omarchy/bin/omarchy-system-reboot, replace line 9:

# Schedule the reboot in the user manager so closing the terminal's systemd
# scope cannot terminate it before it runs. Fall back to system bus if user
# session bus is unavailable (e.g. running from tmux, SSH, or a bare TTY).
if [[ -n ${DBUS_SESSION_BUS_ADDRESS:-} && -n ${XDG_RUNTIME_DIR:-} ]]; then
  systemd-run --user --collect --quiet --on-active="2s" --timer-property=AccuracySec=100ms systemctl reboot --no-wall || exit 1
else
  systemd-run --system --collect --quiet --on-active="2s" --timer-property=AccuracySec=100ms systemctl reboot --no-wall || exit 1
fi
View raw text
## Description

Running `omarchy update` and selecting 'Yes' at the reboot prompt fails with:

```
Failed to connect to user scope bus via local transport: $DBUS_SESSION_BUS_ADDRESS and $XDG_RUNTIME_DIR not defined (consider using --machine=<user>@.host --user to connect to bus of other user)
```

## Root Cause

`omarchy-system-reboot` unconditionally uses `systemd-run --user`, which requires the D-Bus session bus to be accessible. When running from tmux, screen, SSH, or certain terminal contexts, the environment variables `DBUS_SESSION_BUS_ADDRESS` and `XDG_RUNTIME_DIR` are not set.

## Fix

Add a check for the required environment variables and fall back to `systemd-run --system` when the user bus is unavailable.

In `/usr/share/omarchy/bin/omarchy-system-reboot`, replace line 9:

```bash
# Schedule the reboot in the user manager so closing the terminal's systemd
# scope cannot terminate it before it runs. Fall back to system bus if user
# session bus is unavailable (e.g. running from tmux, SSH, or a bare TTY).
if [[ -n ${DBUS_SESSION_BUS_ADDRESS:-} && -n ${XDG_RUNTIME_DIR:-} ]]; then
  systemd-run --user --collect --quiet --on-active="2s" --timer-property=AccuracySec=100ms systemctl reboot --no-wall || exit 1
else
  systemd-run --system --collect --quiet --on-active="2s" --timer-property=AccuracySec=100ms systemctl reboot --no-wall || exit 1
fi
```

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 11:24 UTC