Install omarchy-crash-watch.service into /usr/lib/systemd/user
#6746 added the unit, the binary, the enable-user-units.sh entry, and a migration, but not the install line here -- so omarchy-settings shipped omarchy-crash-watch.service only into the default/ template tree and never into the search path systemd actually reads. install/user/first-run/enable-user-units.sh enables its six units in a single `systemctl --user enable --now` call, so the missing unit failed the whole call. omarchy-provision-first-run only marks first-run-user when every step succeeds, which meant first-run never completed and replayed on every login, re-firing the "Learn Keybindings" and "Update System" notifications. Because enable is atomic, it also left the other five units disabled -- no bluetooth agent, sleep lock, monitor recovery, migrate notifier, or fcitx5. Migration 1786539345 falls back to writing the wants symlink by hand when there is no live user manager, pointing at the /usr/lib path this omission left empty, so existing installs got a dangling symlink too. No new migration is needed: affected installs retry first-run on the next login and succeed, and the dangling symlinks resolve as soon as the file exists at that path. test/shell.d/config-test.sh already asserts this install and fails without it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Jm1hEGtGRUrfqxMbTi1fWe
This commit is contained in:
co-authored by
Claude Opus 5
parent
058eb6392a
commit
2aa5c50e65
@@ -164,6 +164,7 @@ package() {
|
||||
ln -sfn omarchy-migrate-notify.service "$pkgdir/usr/lib/systemd/user/omarchy-update-user-notify.service"
|
||||
install -Dm644 default/systemd/user/omarchy-tailscale-receive.service "$pkgdir/usr/lib/systemd/user/omarchy-tailscale-receive.service"
|
||||
install -Dm644 default/systemd/user/omarchy-fcitx5.service "$pkgdir/usr/lib/systemd/user/omarchy-fcitx5.service"
|
||||
install -Dm644 default/systemd/user/omarchy-crash-watch.service "$pkgdir/usr/lib/systemd/user/omarchy-crash-watch.service"
|
||||
# Marks app.slice (and only app.slice) as a systemd-oomd kill candidate, so
|
||||
# memory pressure costs one app scope instead of the compositor session.
|
||||
# Thresholds live in etc/systemd/oomd.conf.d/10-omarchy.conf.
|
||||
|
||||
Reference in New Issue
Block a user