Skip to content

Fix silently-lost reboot in omarchy-system-reboot #6107

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jondkinney wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

Fix silently-lost reboot in omarchy-system-reboot #6107

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions bin/omarchy-system-reboot
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,8 +6,14 @@

omarchy-state clear re*-required

# Schedule the reboot to happen after closing windows (detached from terminal)
nohup bash -c "sleep 2 && systemctl reboot --no-wall" >/dev/null 2>&1 &
# Schedule the reboot to happen after closing windows.
# Run it as a transient user unit rather than a backgrounded child of this
# script. A `nohup &` child stays inside the terminal's transient systemd scope
# (app-*.scope, created with --collect); closing that terminal below tears the
# scope down and SIGTERMs the still-sleeping child before it can issue the
# reboot, so the reboot is silently lost. A systemd-run unit lives in its own
# cgroup under the user manager and survives the scope teardown.
systemd-run --user --collect --quiet bash -c "sleep 2 && systemctl reboot --no-wall"

# Now close all windows
omarchy-hyprland-window-close-all
Expand Down