Restore the Omarchy screensaver and idle lock after Stay Awake is turned off
Issue #12302 (open) supports the symptom, the reboot trigger, the restart workaround and the hedged cause. The installed and quattro Service.qml both still bind IdleMonitor.enabled to idleEnabled, which is stayAwakeStateLoaded && !stayAwake. PR #12603, which would have kept the monitor subscribed, was closed unmerged (2026-10-01), so the bug is current. omarchy-toggle-idle allow-idle removes ~/.local/state/omarchy/indicators/stay-awake. omarchy restart shell resolves to omarchy-restart-shell. Its source refuses on a locked session with a live locker and re-locks one whose locker died, so the danger text and the 'unlocked only' instruction are right. ~/.config/omarchy/shell.json carries idle.screensaver and idle.lock, and the shell's idle events reach journalctl --user (identifier omarchy-shell, lines such as idle-cycle-cancel), so the verify works. The cause's 'exact layer is a guess' hedge correctly reflects the reporter and the z23 comment. Not exercised: no shell restart on this workstation.
Restarting the shell on a locked session can leave you at a fresh lock screen. Only run it from an unlocked desktop session.
Symptom
I turned Stay Awake off (bar indicator, or omarchy toggle idle allow-idle) but the screensaver and idle lock never come back. omarchy-shell idle status says "enabled":true,"stayAwake":false, yet the machine sits idle for ages and nothing happens. It started after a reboot while Stay Awake was still on.
Cause
Stay Awake is a state file, ~/.local/state/omarchy/indicators/stay-awake, and it survives reboots. If the shell starts while that file exists, the idle service builds its IdleMonitor with enabled: false. When Stay Awake is later turned off, the binding flips to true but the underlying ext_idle_notification_v1 object is apparently never re-created, so the compositor never sends another idle event. The service reports itself healthy the whole time. Reported on 4.0.3 (aarch64) and open upstream. The exact layer is the reporter's suspicion, not confirmed.
Fix
Restart the shell once while Stay Awake is off and the session is **unlocked**:
omarchy toggle idle allow-idle # make sure the state file is gone
ls ~/.local/state/omarchy/indicators/stay-awake 2>/dev/null || echo 'stay-awake off'
omarchy restart shell
To avoid it, turn Stay Awake off before you shut down or reboot, so the next shell starts with idle enabled.
Do **not** run omarchy restart shell from ssh or on a locked session. On a locked session with a dead locker it re-locks and waits for the lock to come back, which leaves you with a lock you have to type the password into.
Verify
Temporarily lower idle.screensaver in ~/.config/omarchy/shell.json to 20 and leave the machine alone. journalctl --user -b | grep -E 'idle-monitor: idle|idle-cycle-start' should show a new cycle after 20 seconds. Put the value back afterwards.