Skip to content

Fix timezone first-run notification --exec - #296

Closed
scottjones wants to merge 2 commits into
quattrofrom
fix/first-run-timezone-exec
Closed

scottjones wants to merge 2 commits into
quattrofrom
fix/first-run-timezone-exec

Conversation

@scottjones

Copy link
Copy Markdown
Collaborator

Why

On a Mac, install.sh does not run omarchy_prompt_timezone (that lives on the x86 ISO / omarchy-provision-owner form). The Mac path is install/user/first-run/timezone.sh: a critical notification if timedatectl is still UTC.

omarchy-notification-send takes --exec <program> [args...] as separate words. This leaf quoted the whole command as one string, so the send failed (exit 1), the toast never appeared, and first-run logged prompt for the timezone as failed. wifi.sh already unquotes --exec.

After an ISO install we reproduced that exact log line on a UTC machine.

Change

--exec omarchy-launch-floating-terminal-with-presentation omarchy-cmd-tzupdate-enhanced

The ISO installer now also asks timezone at copy time (parity with the x86 form). This PR is the first-run fallback when that did not run or the machine is still UTC.

scottjones and others added 2 commits August 29, 2026 15:57
omarchy-notification-send rejects a quoted command string, so the UTC
toast never appeared after an ISO install (wifi.sh already unquotes).
@malik-na

malik-na commented Sep 9, 2026

Copy link
Copy Markdown
Member

#362 carries the same fix plus focused coverage. Please close this as superseded and keep the tested PR as the merge path.

@malik-na malik-na closed this Sep 10, 2026
@malik-na

Copy link
Copy Markdown
Member

Superseded by #377 (same timezone --exec fix). Closing without merge.

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.

2 participants