Order the migration notifier after graphical-session.target

omarchy-migrate-notify.service is a Type=oneshot wanted by
graphical-session.target, and systemd complements a target's Wants= with an
implicit After=, so the target waited for the notifier to exit. The notifier
does not exit quickly: it sends the notification through systemd-run --scope,
which is synchronous, and omarchy-notification-send -a blocks until the user
clicks. The target stayed in activating for as long as the toast was up.

wayland-wm-app-daemon.service is After=graphical-session.target and nothing
wants it, so uwsm-app starts it on demand. Clicking the notification runs
omarchy-launch-floating-terminal-with-presentation, which execs uwsm-app,
which blocks on a systemctl --user restart of that daemon -- a job queued
behind the very target the clicked notifier was holding open. The terminal
never opened; uwsm-app gave up on its own pipe timeout instead.

Declaring After= on the wanted unit suppresses the implicit dependency rather
than forming a cycle, so the target is reached without waiting and the
notifier runs behind it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

This commit is contained in:

David Heinemeier Hansson

2026-07-27 08:41:59 -07:00

co-authored by

Claude Opus 5

parent 2fb33a2a6a

commit c7e327b05a

6 changed files with 18 additions and 6 deletions

									
										docs/migrations.md
									
		+2
		-1
	
												View File
												
				@@ -45,7 +45,8 @@ all pending migrations for the current user in the visible update terminal.

				### At login

				Every graphical login starts `omarchy-migrate-notify.service`, which checks:

				Every graphical login starts `omarchy-migrate-notify.service` after

				`graphical-session.target`. The notifier checks:

				```bash

				omarchy-migrate --pending