Repository navigation
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Natetgmaxwell
left a comment
There was a problem hiding this comment.
Tested on the model where this symptom actually shows up: MacBookPro17,1 (13-inch M1 MacBook Pro, Touch Bar), Omarchy 4.5.0-3, edge, image built 2026-09-23 — so omarchy-mac had never been installed, only omarchy-mac-boot.
Before (stopgap removed):
pacman -Q omarchy-mac→ not found/usr/share/omarchy-platformdid not existomarchy-hw-display→228600000.dsi.0(the Touch Bar's DSI panel)- brightness keys/OSD changed the Touch Bar;
apple-panel-blwas untouched
Ran migrations/1792657167.sh from this branch with bash -euo pipefail (pkexec stood in for the sudo line, as this was outside an update):
omarchy-pkg-add omarchy-macinstalledomarchy-mac 0.2.3-2omarchy-lifecycle-dispatch setup-systemenabledomarchy-wifi-resume-fix.service, presetspeakersafetyd, and rebuilt the initramfs cleanlysetup-userenabledomarchy-asahi-mic.service- exit 0; a second full run installed nothing, changed nothing, exit 0
After:
omarchy-hw-display→apple-panel-bl/usr/share/omarchy-platform/displays.confcarriesbacklight-skip 228600000.dsi.0,backlight-prefer apple-panel-bl,ddc-require-connector-ddcbrightnessctl -d apple-panel-bl set 50%→ 255/509 while228600000.dsi.0stayed 255/255; restored 509/509omarchy-brightness-displayreports 100
Same benign runtime mismatch you saw on 0.1.4: 4.5.0-3 still has no omarchy-cmd-electron-gl-wrap, so both setup steps print "Skipping Electron ...". Not blocking for this migration, just confirming it on the Touch Bar model too.
One thing worth considering: the migration reruns setup-system for every user on the machine, so a second user's login-time run would ask for sudo again for a machine-wide step. A root-owned marker written after setup-system succeeds would skip it for later users while still retrying an interrupted run. Current behaviour is correct, just noisier — up to you.
Problem
omarchy-macjoined the Apple Silicon defaults (install/omarchy-aarch64-apple.packages) in #14431, but updates install no new defaults, and no migration adds it. A Mac installed before then runs 4.5 without it.On such a Mac (16-inch MacBook Pro, M1 Max, 4.5.0-rc1),
pacmanhad never installedomarchy-mac. Its greeter wait for Apple's display controller (sddm.service.d/10-omarchy-mac-wait-for-display.conf) was therefore missing. On one boot, Hyprland started at 35.6 s andapple-drminitialized at 36.2 s. Hyprland kept the vanished simpledrm output asUnknown-1, logged about 14,600atomic drm: failed to create a damage bloberrors, and never droveeDP-1. The built-in display stayed black until the session was restarted. The audio watchdog, the Wi-Fi resume fix and the mic setup were missing too.Fix
A migration that, on
aarch64-apple, installsomarchy-macand runs its system and user setup throughomarchy-lifecycle-dispatch, as provisioning does.omarchy-pkg-addskips a package that is already installed, and both setups are idempotent and rebuild no boot file, so a Mac that already has it only reruns setup. Each user gets the user setup.The hardware video-decode defaults (
avd-fw,libva-v4l2_request-avd) are missing on such Macs as well, but they are defaults an owner may remove, so this leaves them alone.Testing
bash -npasses.image-deferred-hardware,platform-setup,privileged-heredocand the tests that read every migration pass.omarchy-mac0.1.4-1 and exited 0.sddm.servicenow carries10-omarchy-mac-wait-for-display.conf,omarchy-wifi-resume-fixis enabled, andomarchy-asahi-micis running. A second run reinstalls nothing and exits 0.apple-drminitialized at 13.17 s, SDDM started at 13.22 s and Hyprland at 14.27 s. Hyprland named the built-in paneleDP-1.Skipping Electron launchers: the runtime has no omarchy-cmd-electron-gl-wrap, becauseomarchy-mac0.1.4 expects a command 4.5 does not ship. It skips that step cleanly; the mismatch belongs toomarchy-mac, not to this migration.