David Heinemeier HanssonandGitHub
2cc3510d2a
* Offer an AI diagnosis when a process crashes systemd-coredump journals every core dump under a known MESSAGE_ID with the crashing program, pid, and signal as structured fields. omarchy-crash-watch follows that stream and raises a "Process crashed: <program>" toast; clicking it opens omarchy-agent-crash, which briefs the default agent on the crash. The toast goes through omarchy-notification-send --exec rather than a libnotify action, because the shell runs clicks from its own omarchy-exec hint and never emits ActionInvoked. It keeps the default "omarchy-action" app name too, the only one shouldBypassDnd() lets through -- a crash being the last notification worth swallowing. It stays quiet until an agent is configured, since a diagnosis is all it offers. The method lives in a diagnose-crash skill rather than the prompt, so it is edited in one place and works with whichever agent is default. It covers investigating the core, and reporting a confirmed Omarchy bug upstream: scoped to bugs Omarchy controls, searched for duplicates first, only with the user's agreement, and signed with the model and harness that produced it. A migration reaches existing installs, whose skill symlinks and unit enablement would otherwise sit behind one-time setup paths. * Let the diagnosis clean up the core it extracted "Do not modify or delete anything" contradicted the symbolization step right above it, which writes a core to a temp file and deletes it on exit. Read literally, the core survives -- and the same section warns it holds passwords and tokens. The prohibition is about the system, not about your own scratch. * Do not spend a crash toast on a dead notification server The shell owns org.freedesktop.Notifications, so its own crash takes the notification server down with it -- and a shell crash is exactly what you want told about. The toast was sent once into that gap and the dedupe window was recorded regardless, so the rest of the crash loop went quiet for a minute and `journalctl -n 0` never replays what was missed. It now waits for the restarted shell to reclaim the bus name, as omarchy-migrate-notify already does, and only a delivered toast starts the dedupe window.
22 lines
864 B
Bash
Executable File
22 lines
864 B
Bash
Executable File
#!/bin/bash
|
|
|
|
# Enable AND start the user systemd units we ship. Runs at first-run rather
|
|
# than at finalize-user time because the user manager isn't live during the
|
|
# ISO chroot — by first-run, the Hyprland/uwsm session is up and
|
|
# `systemctl --user enable --now` both writes the correct .wants symlinks
|
|
# (based on each unit's [Install]/WantedBy) and starts the services so the
|
|
# first session has bluetooth pairing, sleep lock, etc. live immediately
|
|
# instead of waiting for the next login. ConditionPath* in the unit files
|
|
# keep the enabled units inert on hardware they don't apply to.
|
|
|
|
set -euo pipefail
|
|
|
|
systemctl --user daemon-reload
|
|
systemctl --user enable --now \
|
|
bt-agent.service \
|
|
omarchy-recover-internal-monitor.service \
|
|
omarchy-sleep-lock.service \
|
|
omarchy-migrate-notify.service \
|
|
omarchy-fcitx5.service \
|
|
omarchy-crash-watch.service
|