Skip to content

fix(update): guard confirm_reboot in omarchy-update-restart under unattended runs - #9100

Open
harshithnadig wants to merge 1 commit into
omacom:quattrofrom
harshithnadig:fix/update-restart-unattended-guard
Open

fix(update): guard confirm_reboot in omarchy-update-restart under unattended runs#9100
harshithnadig wants to merge 1 commit into
omacom:quattrofrom
harshithnadig:fix/update-restart-unattended-guard

Conversation

@harshithnadig

Copy link
Copy Markdown

Problem

In #9079, running omarchy update -y in unattended mode can still hang on interactive input if the Linux kernel, Hyprland binary, or reboot-required state file is present.

While omarchy-update exports OMARCHY_UPDATE_UNATTENDED=1 on -y, confirm_reboot() in bin/omarchy-update-restart was calling gum confirm "$1" unconditionally without an unattended check.

Solution

Check ${OMARCHY_UPDATE_UNATTENDED:-} in confirm_reboot(). When unattended, log the reboot notification and return without blocking, allowing the remaining update and shell reload steps to complete cleanly.

Fixes #9079

When running 'omarchy update -y', OMARCHY_UPDATE_UNATTENDED=1 is exported
so that update steps run without waiting for interactive input.
However, confirm_reboot() previously called 'gum confirm' unconditionally
if the kernel, hyprland, or state files indicated a reboot was needed,
causing unattended updates to hang.

Check OMARCHY_UPDATE_UNATTENDED and report that a reboot is pending
instead of prompting interactively.

Fixes omacom#9079
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

omarchy-update-restart: confirm_reboot has no unattended guard, still hangs under -y

1 participant